Long landing rollout — N327LX
KBCB · 312025-11-22 15:54 UTC· KASH → KBCB· BOSTON POST LEASING LLC· F2TH
N327LX (Boston Post Leasing) was operating from KASH to KBCB on 2025-11-22. SkyMeter detected a long landing rollout at Virginia Tech Montgomery Executive Airport (KBCB) on runway 31 at 15:54 UTC. Trace data at the event: 2073 ft AGL, 0 kt GS. Approach stability score: 61/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 8 kt wind, 1 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)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
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 31
- 2073 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 61/100
- 8 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KBCB 070515Z AUTO 00000KT 10SM CLR 08/08 A3015 RMK AO2 T00840082
Flight context
- N327LX
- Boston Post Leasing
- F2TH
- KASH → KBCB
- 2025-11-22 15:54 UTC
- KBCB runway 31
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