Unstable approach — N628TM
KMQI · 232026-07-18 11:50 UTC· KHFY → KMQI· FEDAIR LLC· C25A
N628TM (Fedair) was operating from KHFY to KMQI on 2026-07-18. SkyMeter detected a low approach-stability score at Dare County Regional Airport (KMQI) on runway 23 at 11:50 UTC. Trace data at the event: 1144 ft AGL, 133 kt GS. Approach stability score: 36/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 8 kt wind, 1 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/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3970 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3971 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4005 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7169 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV
View FAA NOTAM → - SECURITY6/7194 2026-07-03 16:07Z – 2026-07-21 03:59Z SFC–400 ft
Columbus, OH
View FAA NOTAM → - SECURITY6/7197 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Louisville, KY
View FAA NOTAM → - SECURITY6/7218 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Cinncinati, OH
View FAA NOTAM → - SECURITY6/7226 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Milford, OH
View FAA NOTAM → - HAZARDS6/5843 2026-07-14 23:37Z – 2026-07-22 23:45Z SFC–4,200 ft
18NM SW WAYNESBORO, VA, Tuesday, July 14, 2026 through Wednesday, July 22, 2026 UTC
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 23
- 1144 ft AGL at event
- 133 kt ground speed
- 0 fpm vertical
- Approach stability 36/100
- 8 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KMQI 160435Z AUTO 10004KT 10SM SCT043 22/15 A3032 RMK AO2 T02240146
Flight context
- N628TM
- Fedair
- C25A
- KHFY → KMQI
- 2026-07-18 11:50 UTC
- KMQI runway 23
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