Long landing rollout — FLE648
CZBA · 142026-08-04 00:35 UTC· CYWG → CZBA· Flair Airlines Ltd· B38M
FLE648 (Flair Airlines) was operating from CYWG to CZBA on 2026-08-04. SkyMeter detected a long landing rollout at Burlington Executive (CZBA) on runway 14 at 00:35 UTC. Trace data at the event: 557 ft AGL, 4 kt GS. METAR at the time reported 5 kt wind, 3 kt crosswind component. 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)- HAZARDS6/6777 2026-07-19 19:05Z – 2026-08-20 07:00Z SFC–7,000 ft
10NM N ELY, MN, Sunday, July 19, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/6779 2026-07-19 19:09Z – 2026-08-20 07:00Z SFC–7,000 ft
20NM N ELY, MN, Sunday, July 19, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/1033 2026-08-03 10:00Z – 2026-08-10 02:00Z SFC–7,000 ft
25NM NW ELY, MN, Monday, August 3, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/1034 2026-08-03 10:00Z – 2026-08-10 02:00Z SFC–7,000 ft
13NM N ELY, MN, Monday, August 3, 2026 through Monday, August 10, 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 14
- 557 ft AGL at event
- 4 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 3 kt crosswind component
Flight context
- FLE648
- Flair Airlines
- B38M
- CYWG → CZBA
- 2026-08-04 00:35 UTC
- CZBA runway 14
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