Long landing rollout — N8DZ
KBJC · 12R2026-06-18 22:07 UTC· KCMH → KBJC· PILATUS BUSINESS AIRCRAFT LTD· PC24
N8DZ (Pilatus Business Aircraft) was operating from KCMH to KBJC on 2026-06-18. SkyMeter detected a long landing rollout at Rocky Mountain Metropolitan Airport (KBJC) on runway 12R at 22:07 UTC. Trace data at the event: 5590 ft AGL, 3 kt GS. METAR at the time reported 7 kt wind, 6 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)- SECURITY6/4118 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CARMEL, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4128 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WESTFIELD, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/5706 2026-06-11 14:00Z – 2026-06-23 04:00Z SFC–400 ft
Omaha, NE, Thursday, June 11, 2026 through Tuesday, June 23, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/7816 2026-06-18 20:30Z – 2026-06-18 22:30Z SFC–16,000 ft
Columbus, OH, Thursday, June 18, 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 12R
- 5590 ft AGL at event
- 3 kt ground speed
- 0 fpm vertical
- 7 kt wind
- 6 kt crosswind component
- 16,093 m visibility
- KBJC 181950Z 23003KT 10SM CLR 29/06 A3018
Flight context
- N8DZ
- Pilatus Business Aircraft
- PC24
- KCMH → KBJC
- 2026-06-18 22:07 UTC
- KBJC runway 12R
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