Long landing rollout — N811JL
PABV · 19R2026-07-03 23:49 UTC· KBFI → PABV· MARLIN22 LLC· C525
N811JL (Marlin22) was operating from KBFI to PABV on 2026-07-03. SkyMeter detected a long landing rollout at Birchwood Airport (PABV) on runway 19R at 23:49 UTC. Trace data at the event: 0 ft AGL, 3 kt GS, 0 fpm vertical. METAR at the time reported 3 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)- SECURITY6/4011 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BELLEVUE, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4013 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Seattle, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4034 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Renton, WA, Monday, June 1, 2026 through Monday, July 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 19R
- 0 ft AGL at event
- 3 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- PABV 180956Z AUTO 00000KT 10SM -RA BKN065 OVC080 09/08 A2993 RMK AO2 RAB29 SLP134 P0000 T00940078 $
Flight context
- N811JL
- Marlin22
- C525
- KBFI → PABV
- 2026-07-03 23:49 UTC
- PABV runway 19R
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