Unstable approach — N793DC
KBIL · 28R2026-08-23 19:15 UTC· KSFF → KBIL· BILLINGS CLINIC· BE20
N793DC (Billings Clinic) was operating from KSFF to KBIL on 2026-08-23. SkyMeter detected a low approach-stability score at Billings Logan International Airport (KBIL) on runway 28R at 19:15 UTC. Trace data at the event: 4690 ft AGL, 176 kt GS. Approach stability score: 30/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 9 kt wind, 9 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/4911 2026-08-13 15:00Z – 2026-08-28 04:00Z SFC–7,500 ft
10NM W LEWISTON, ID, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/5136 2026-08-14 22:00Z – 2026-08-29 04:00Z SFC–10,000 ft
10NM E HAMILTON, MT, Friday, August 14, 2026 through Saturday, August 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/5460 2026-08-17 12:00Z – 2026-08-30 04:00Z SFC–10,500 ft
9NM SW HAMILTON, MT, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/6215 2026-08-19 14:00Z – 2026-09-01 04:00Z SFC–11,000 ft
12NM W PLAINS, MT, Wednesday, August 19, 2026 through Tuesday, September 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/6599 2026-08-20 13:00Z – 2026-09-03 03:00Z SFC–11,000 ft
21NM SE HAMILTON, MT, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/6719 2026-08-20 14:00Z – 2026-09-02 04:00Z SFC–11,000 ft
12NM W PLAINS, MT, Thursday, August 20, 2026 through Wednesday, September 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/6723 2026-08-20 14:00Z – 2026-09-03 04:00Z SFC–9,000 ft
16NM E BIG TIMBER, MT, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/4976 2026-08-20 17:30Z – 2026-08-23 22:30Z
BILLINGS, MT, Thursday, August 20, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/4977 2026-08-20 17:30Z – 2026-08-23 22:30Z SFC–17,999 ft
Billings, MT, Thursday, August 20, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6935 2026-08-21 15:00Z – 2026-09-04 04:00Z SFC–10,000 ft
48NM NE OROFINO, ID, Friday, August 21, 2026 through Friday, September 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/7095 2026-08-22 14:00Z – 2026-09-05 04:00Z SFC–11,000 ft
10NM W PLAINS, MT, Saturday, August 22, 2026 through Saturday, September 5, 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 28R
- 4690 ft AGL at event
- 176 kt ground speed
- 0 fpm vertical
- Approach stability 30/100
- 9 kt wind
- 9 kt crosswind component
- 16,093 m visibility
- KBIL 160653Z 02007KT 10SM FEW250 12/03 A3003 RMK AO2 SLP154 T01170033 402220061
Flight context
- N793DC
- Billings Clinic
- BE20
- KSFF → KBIL
- 2026-08-23 19:15 UTC
- KBIL runway 28R
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