Unstable approach — N725FH

PAHO · 22

2026-09-03 01:29 UTC· 2AK4 PAHO· EMERALD AIR SERVICE INC· DHC2

N725FH (Emerald AIR Service) was operating from 2AK4 to PAHO on 2026-09-03. SkyMeter detected a low approach-stability score at Homer Airport (PAHO) on runway 22 at 01:29 UTC. Trace data at the event: 539 ft AGL, 77 kt GS. Approach stability score: 28/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 9 kt wind, 5 kt crosswind component, 16,093 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.

Pilot review data

  • Runway 22
  • 539 ft AGL at event
  • 77 kt ground speed
  • 0 fpm vertical
  • Approach stability 28/100
  • 9 kt wind
  • 5 kt crosswind component
  • 16,093 m visibility
  • PAHO 161153Z AUTO 24016G30KT 10SM BKN038 OVC046 11/06 A2994 RMK AO2 PK WND 23030/1147 SLP139 60000 70047 T01060061 10111 20094 53003 TSNO $

Flight context

  • N725FH
  • Emerald AIR Service
  • DHC2
  • 2AK4 → PAHO
  • 2026-09-03 01:29 UTC
  • PAHO runway 22

All events on this flight

Unstable approach 01:29:21 UTC · PAHO runway 22 · 539 ft AGL · 77 kt GS
Long landing rollout 01:31:04 UTC · PAHO runway 22 · 16 ft AGL · 5 kt GS

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· PAHO