Long landing rollout — N405DC

KBCT · 05

2026-08-31 17:42 UTC· KTEB → KBCT· COS AIR LLC· LJ60

▶ Replay 📊 Analyse

N405DC (COS AIR) was operating from KTEB to KBCT on 2026-08-31. SkyMeter detected a long landing rollout at Boca Raton Airport (KBCT) on runway 05 at 17:42 UTC. Trace data at the event: 52 ft AGL, 4 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 3 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/7351 2026-08-27 12:00Z – 2026-10-13 03:00Z SFC–400 ft

    Timonium, MD, Thursday, August 27, 2026 through Tuesday, October 13, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/8897 2026-08-31 12:00Z – 2026-08-31 20:30Z SFC–400 ft

    STOYSTOWN, PA, Monday, August 31, 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 05
  • 52 ft AGL at event
  • 4 kt ground speed
  • 0 fpm vertical
  • 4 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • METAR KBCT 152253Z 07007KT 10SM SCT020 30/25 A3006 RMK LTG DSNT SW

Flight context

  • N405DC
  • COS AIR
  • LJ60
  • KTEB → KBCT
  • 2026-08-31 17:42 UTC
  • KBCT runway 05

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

SkyMeter · trace data observed via ADS-B· KBCT