Unstable approach — N156ML
KEQY · 052026-05-31 19:43 UTC· KMMU → KEQY· ATP JET AIRCRAFT LLC· C25A
N156ML (ATP JET Aircraft) was operating from KMMU to KEQY on 2026-05-31. SkyMeter detected a low approach-stability score at Charlotte-Monroe Executive Airport (KEQY) on runway 05 at 19:43 UTC. Trace data at the event: 1781 ft AGL, 146 kt GS. METAR at the time reported 3 kt wind, 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/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft
Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 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 05
- 1781 ft AGL at event
- 146 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- METAR KEQY 122253Z AUTO 33009G16KT 10SM OVC070 15/02 A2965 RMK AO2 SLP047 T01500022
Flight context
- N156ML
- ATP JET Aircraft
- C25A
- KMMU → KEQY
- 2026-05-31 19:43 UTC
- KEQY runway 05
All events on this flight
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