Unstable approach — N923FP
WA09 · 242026-08-16 17:44 UTC· KYKM → WA09· F M P ENTERPRISES LLC· B350
N923FP (F M P Enterprises) was operating from KYKM to WA09 on 2026-08-16. SkyMeter detected a low approach-stability score at Roche Harbor Airport (WA09) on runway 24 at 17:44 UTC. Trace data at the event: 1163 ft AGL, 120 kt GS. Approach stability score: 36/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 4 kt wind, 4 kt crosswind component. 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/2492 2026-08-06 05:00Z – 2026-08-19 05:00Z SFC–13,500 ft
26NM NW LEAVENWORTH, WA, Thursday, August 6, 2026 through Wednesday, August 19, 2026 UTC
View FAA NOTAM → - HAZARDS6/2750 2026-08-07 00:45Z – 2026-08-22 03:00Z SFC–10,000 ft
17NM NW CLE ELUM, WA, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/2887 2026-08-07 20:30Z – 2026-08-22 03:00Z SFC–10,000 ft
2NM NE DARRINGTON, WA, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/2901 2026-08-08 00:45Z – 2026-08-21 05:00Z SFC–10,000 ft
37NM SE TACOMA, WA, Saturday, August 8, 2026 through Friday, August 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/2919 2026-08-08 15:00Z – 2026-08-23 04:00Z SFC–10,000 ft
2NM NE DARRINGTON, WA, Saturday, August 8, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/3089 2026-08-09 00:45Z – 2026-08-22 05:00Z SFC–13,500 ft
26NM NW LEAVENWORTH, WA, Sunday, August 9, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/3099 2026-08-09 02:45Z – 2026-08-23 05:00Z SFC–13,500 ft
26NM NW LEAVENWORTH, WA, Sunday, August 9, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/3105 2026-08-09 05:00Z – 2026-08-24 04:00Z SFC–10,000 ft
17NM NW CLE ELUM, WA, Sunday, August 9, 2026 through Monday, August 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4102 2026-08-12 14:00Z – 2026-08-27 04:00Z SFC–10,000 ft
17NM NW CLE ELUM, WA, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC
View FAA NOTAM → - HAZARDS6/4112 2026-08-12 14:00Z – 2026-08-27 04:00Z SFC–10,000 ft
17NM NW CLE ELUM, WA, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC
View FAA NOTAM → - HAZARDS6/5135 2026-08-14 18:00Z – 2026-08-29 04:00Z SFC–13,500 ft
26NM NW LEAVENWORTH, WA, Friday, August 14, 2026 through Saturday, August 29, 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.
Pilot review data
- Runway 24
- 1163 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 36/100
- 4 kt wind
- 4 kt crosswind component
Flight context
- N923FP
- F M P Enterprises
- B350
- KYKM → WA09
- 2026-08-16 17:44 UTC
- WA09 runway 24
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