Unstable approach — N254PV

N254PV (Sivu Transportation) was operating from KBFI to PAFA on 2026-08-31. SkyMeter detected a low approach-stability score at Fairbanks International Airport (PAFA) on runway 20 at 03:25 UTC. Trace data at the event: 1410 ft AGL, 135 kt GS. METAR at the time reported 4 kt wind, 1 kt crosswind component, 4,828 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

• HAZARDS6/5939 2026-08-18 14:00Z – 2026-08-31 05:00Z SFC–10,000 ft

  21NM S PORT ANGELES, WA, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5943 2026-08-18 18:00Z – 2026-08-31 07:00Z SFC–4,000 ft

  1NM N TOK, AK, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6610 2026-08-20 18:00Z – 2026-08-31 07:00Z SFC–5,000 ft

  1NM N TOK, AK, Thursday, August 20, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9143 2026-08-30 14:00Z – 2026-09-13 06:00Z SFC–4,000 ft

  1NM N TOK, AK, Sunday, August 30, 2026 through Sunday, September 13, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/7549 2026-08-30 23:59Z – 2026-09-01 07:30Z SFC–400 ft

  Seattle, WA, Sunday, August 30, 2026 through Tuesday, September 1, 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.

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