Unstable approach — N724LS
KDAL · 13L2026-05-23 01:38 UTC· KPWK → KDAL· FIVE TEX AVIATION LLC· C25B
N724LS (Five TEX Aviation) was operating from KPWK to KDAL on 2026-05-23. SkyMeter detected a low approach-stability score at Dallas Love Field (KDAL) on runway 13L at 01:38 UTC. Trace data at the event: 1575 ft AGL, 106 kt GS. METAR at the time reported 9 kt wind, 4 kt crosswind component, 16,093 m visibility. 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/1676 2026-05-20 12:00Z – 2026-05-24 23:00Z SFC–400 ft
McKinney, TX, Wednesday, May 20, 2026 through Sunday, May 24, 2026 Local
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 13L
- 1575 ft AGL at event
- 106 kt ground speed
- 0 fpm vertical
- 9 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KDAL 282353Z 15011KT 10SM FEW080 SCT250 37/19 A2980 RMK AO2 SLP081 T03670194 10378 20350 56009
Flight context
- N724LS
- Five TEX Aviation
- C25B
- KPWK → KDAL
- 2026-05-23 01:38 UTC
- KDAL runway 13L
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