Long landing rollout — N4365U
PAFA · 02R2026-04-04 23:03 UTC· WRIGHT AIR SERVICE INC· C208
N4365U (Wright AIR Service) was inbound to PAFA on 2026-04-04. SkyMeter detected a long landing rollout at Fairbanks International Airport (PAFA) on runway 02R at 23:03 UTC. Trace data at the event: 0 ft AGL, 11 kt GS, 0 fpm vertical. Approach stability score: 50/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 3 kt wind, 11,265 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/4925 2026-03-08 10:00Z – 2026-11-01 09:59Z SFC–360 ft
CLEAR, AK, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/4926 2026-03-08 10:00Z – 2026-11-01 12:00Z SFC–2,600 ft
CLEAR, AK, Sunday, March 8, 2026 through Sunday, November 1, 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 02R
- 0 ft AGL at event
- 11 kt ground speed
- 0 fpm vertical
- Approach stability 50/100
- 3 kt wind
- 0 kt crosswind component
- 11,265 m visibility
- PAFA 162053Z 18004KT 7SM -RA FEW013 BKN038 OVC050 08/07 A2976 RMK AO2 SLP083 P0006 60012 T00830072 53012 $
Flight context
- N4365U
- Wright AIR Service
- C208
- 2026-04-04 23:03 UTC
- PAFA runway 02R
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