Unstable approach — N345TR
KLNC · 132026-07-16 01:48 UTC· AQUA AIR LLC· WW24
N345TR (Aqua AIR) was inbound to KLNC on 2026-07-16. SkyMeter detected a low approach-stability score at Lancaster Airport (KLNC) on runway 13 at 01:48 UTC. Trace data at the event: 1583 ft AGL, 146 kt GS. Approach stability score: 33/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 2 kt wind, 1 kt crosswind component. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/3705 2026-05-29 05:00Z – 2026-07-20 08:00Z SFC–400 ft
DALLAS, TX, Friday, May 29, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z
STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z
OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/4019 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
IRVING, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4025 2026-06-01 05:00Z – 2026-07-21 04:59Z
DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/4022 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3952 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Stillwater, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3997 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NORMAN, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3999 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
ARLINGTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4002 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4008 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4009 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/6842 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft
Fort Worth, TX
View FAA NOTAM → - SECURITY6/6844 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Frisco, TX
View FAA NOTAM → - SECURITY6/6843 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Frisco, TX
View FAA NOTAM → - HAZARDS6/2597 2026-07-02 04:41Z – 2026-07-16 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/2812 2026-07-03 02:53Z – 2026-07-17 04:00Z SFC–17,000 ft
1NM N OURAY, CO, Friday, July 3, 2026 through Friday, July 17, 2026 UTC
View FAA NOTAM → - HAZARDS6/2942 2026-07-05 12:00Z – 2026-07-19 04:00Z SFC–17,000 ft
2NM W LEADVILLE, CO, Sunday, July 5, 2026 through Sunday, July 19, 2026 UTC
View FAA NOTAM → - HAZARDS6/3007 2026-07-06 12:00Z – 2026-07-20 04:00Z SFC–17,000 ft
1NM W LEADVILLE, CO, Monday, July 6, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3274 2026-07-07 00:35Z – 2026-07-20 04:00Z SFC–17,000 ft
1NM W LEADVILLE, CO, Tuesday, July 7, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3801 2026-07-08 01:49Z – 2026-07-23 04:00Z SFC–15,000 ft
1NM W PUEBLO, CO, Wednesday, July 8, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/4561 2026-07-10 04:00Z – 2026-07-24 04:00Z SFC–16,500 ft
19NM NE OURAY, CO, Friday, July 10, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4562 2026-07-10 12:00Z – 2026-07-24 05:00Z SFC–17,000 ft
3NM W LEADVILLE, CO, Friday, July 10, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/5450 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft
19NM NE OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/5451 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft
1NM N OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 2026 UTC
View FAA NOTAM → - SECURITY6/4573 2026-07-14 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft
Dallas, TX, Tuesday, July 14, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - SECURITY6/6784 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft
Denton, TX
View FAA NOTAM → - SECURITY6/6841 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft
Fort Worth, TX
View FAA NOTAM → - SECURITY6/6849 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft
Irving, TX
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 13
- 1583 ft AGL at event
- 146 kt ground speed
- 0 fpm vertical
- Approach stability 33/100
- 2 kt wind
- 1 kt crosswind component
Flight context
- N345TR
- Aqua AIR
- WW24
- 2026-07-16 01:48 UTC
- KLNC runway 13
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data