Unstable approach — WWI91
KMQJ · 252026-06-30 00:08 UTC· KBNA → KMQJ· ONEIDA II LLC· GLF4
WWI91 (Oneida II) was operating from KBNA to KMQJ on 2026-06-30. SkyMeter detected a low approach-stability score at Indianapolis Regional Airport (KMQJ) on runway 25 at 00:08 UTC. Trace data at the event: 1979 ft AGL, 171 kt GS. METAR at the time reported 6 kt wind, 5 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/4119 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 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 25
- 1979 ft AGL at event
- 171 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- METAR KMQJ 071555Z AUTO 23009KT 10SM CLR 23/10 A2993 RMK AO2 T02260097
Flight context
- WWI91
- Oneida II
- GLF4
- KBNA → KMQJ
- 2026-06-30 00:08 UTC
- KMQJ runway 25
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