Long landing rollout — N793DC
KBIL · 28L2026-08-22 02:36 UTC· KBIL → KBIL· BILLINGS CLINIC· BE20
N793DC (Billings Clinic) was operating from KBIL to KBIL on 2026-08-22. SkyMeter detected a long landing rollout at Billings Logan International Airport (KBIL) on runway 28L at 02:36 UTC. Trace data at the event: 3585 ft AGL, 1 kt GS. METAR at the time reported 9 kt wind, 7 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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 →
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 28L
- 3585 ft AGL at event
- 1 kt ground speed
- 0 fpm vertical
- 9 kt wind
- 7 kt crosswind component
- 16,093 m visibility
- KBIL 162353Z 07010KT 10SM FEW230 21/05 A3023 RMK AO2 SLP224 T02060050 10211 20172 53002
Flight context
- N793DC
- Billings Clinic
- BE20
- KBIL → KBIL
- 2026-08-22 02:36 UTC
- KBIL runway 28L
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