Unstable approach — CYT72
KFAR · 362026-06-18 01:59 UTC· KBIS → KFAR· LONGREACH AIR LLC· SF50
CYT72 (Longreach AIR) was operating from KBIS to KFAR on 2026-06-18. SkyMeter detected a low approach-stability score at Hector International Airport (KFAR) on runway 36 at 01:59 UTC. Trace data at the event: 1988 ft AGL, 124 kt GS. METAR at the time reported 7 kt wind, 2 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/4348 2026-03-08 07:00Z – 2026-11-01 06:59Z SFC–2,400 ft
GRAND FORKS AFB, ND, Sunday, March 8, 2026 through Sunday, November 1, 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 36
- 1988 ft AGL at event
- 124 kt ground speed
- 0 fpm vertical
- 7 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KFAR 202253Z AUTO 31020G32KT 10SM FEW065 30/15 A2971 RMK AO2 PK WND 31033/2204 SLP057 T03000150
Flight context
- CYT72
- Longreach AIR
- SF50
- KBIS → KFAR
- 2026-06-18 01:59 UTC
- KFAR runway 36
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