Unstable approach — N525F
KBZN · 122026-07-31 02:21 UTC· KJYO → KBZN· ELEMENT AVIATION SERVICES LLC· C25A
N525F (Element Aviation Services) was operating from KJYO to KBZN on 2026-07-31. SkyMeter detected a low approach-stability score at Gallatin Field (KBZN) on runway 12 at 02:21 UTC. Trace data at the event: 5499 ft AGL, 170 kt GS. METAR at the time reported 3 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)- HAZARDS6/6894 2026-07-20 14:02Z – 2026-08-03 04:00Z SFC–12,500 ft
12NM NW CRAIG, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/6900 2026-07-20 14:42Z – 2026-08-03 04:00Z SFC–13,500 ft
11NM SW KREMMLING, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/7220 2026-07-21 04:00Z – 2026-08-04 04:00Z SFC–12,000 ft
19NM SW MEEKER, CO, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/7221 2026-07-21 04:00Z – 2026-08-04 04:00Z SFC–13,500 ft
7NM SE STEAMBOAT SPRINGS, CO, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/7702 2026-07-22 13:08Z – 2026-08-05 04:00Z SFC–11,500 ft
11NM SW CRAIG, CO, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/8871 2026-07-27 14:00Z – 2026-08-09 04:00Z SFC–8,000 ft
83NM N SPEARFISH, SD, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/9566 2026-07-28 17:15Z – 2026-08-11 04:00Z SFC–10,000 ft
33NM SW PHILIP, SD, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/9803 2026-07-28 21:15Z – 2026-08-01 23:45Z SFC–200 ft
0.5NM NE MENASHA, WI, Tuesday, July 28, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/9861 2026-07-29 00:45Z – 2026-08-01 04:00Z SFC–12,500 ft
19NM NW GRAND JUNCTION, CO, Wednesday, July 29, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/9884 2026-07-29 12:00Z – 2026-08-12 04:00Z SFC–12,500 ft
19NM NW GRAND JUNCTION, CO, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/9880 2026-07-29 14:00Z – 2026-08-12 03:00Z SFC–9,000 ft
26NM E MILES CITY, MT, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/8930 2026-07-30 16:00Z – 2026-08-03 03:00Z SFC–400 ft
Chicago, IL, Thursday, July 30, 2026 through Monday, August 3, 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 12
- 5499 ft AGL at event
- 170 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KBZN 161456Z 00000KT 10SM CLR 08/03 A3024 RMK AO2 SLP228 T00830028 53022 $
Flight context
- N525F
- Element Aviation Services
- C25A
- KJYO → KBZN
- 2026-07-31 02:21 UTC
- KBZN runway 12
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