Unstable approach — RAX285
KPTK · 27L2026-05-25 23:50 UTC· KSNA → KPTK· ROYAL AIR FREIGHT INC· FA20
RAX285 (Royal AIR Freight) was operating from KSNA to KPTK on 2026-05-25. SkyMeter detected a low approach-stability score at Oakland County International Airport (KPTK) on runway 27L at 23:50 UTC. Trace data at the event: 2094 ft AGL, 161 kt GS. Approach stability score: 45/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 7 kt wind, 4 kt crosswind component, 3,219 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/0618 2026-05-15 13:00Z – 2026-05-28 04:00Z SFC–13,500 ft
22NM NE RUIDOSO, NM, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/0607 2026-05-15 14:00Z – 2026-05-28 04:00Z SFC–12,000 ft
30NM SW NEPHI, UT, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/0887 2026-05-16 18:37Z – 2026-05-30 04:00Z SFC–10,500 ft
19NM SW TUCUMCARI, NM, Saturday, May 16, 2026 through Saturday, May 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/1015 2026-05-18 00:28Z – 2026-06-01 04:00Z SFC–15,500 ft
22NM NE RUIDOSO, NM, Monday, May 18, 2026 through Monday, June 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/1358 2026-05-19 00:52Z – 2026-06-02 02:00Z SFC–10,000 ft
5NM S CAMPO, CO, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/1626 2026-05-19 22:38Z – 2026-06-02 04:00Z SFC–15,500 ft
22NM NE RUIDOSO, NM, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/2366 2026-05-22 06:00Z – 2026-06-05 04:00Z SFC–10,000 ft
12NM S PRESCOTT, AZ, Friday, May 22, 2026 through Friday, June 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/2354 2026-05-22 12:00Z – 2026-06-04 04:00Z SFC–15,500 ft
22NM NE RUIDOSO, NM, Friday, May 22, 2026 through Thursday, June 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/2580 2026-05-24 14:00Z – 2026-05-30 04:00Z SFC–10,000 ft
30NM SW WINNEMUCCA, NV, Sunday, May 24, 2026 through Saturday, May 30, 2026 UTC
View FAA NOTAM → - SECURITY6/1987 2026-05-25 12:00Z – 2026-05-25 20:00Z SFC–400 ft
Boulder, CO, Monday, May 25, 2026 Local
View FAA NOTAM → - SECURITY6/2319 2026-05-25 12:00Z – 2026-05-25 20:00Z SFC–400 ft
Boulder, CO, Monday, May 25, 2026 Local
View FAA NOTAM → - HAZARDS6/2645 2026-05-25 14:00Z – 2026-05-30 04:00Z SFC–10,000 ft
30NM SW WINNEMUCCA, NV, Monday, May 25, 2026 through Saturday, May 30, 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 27L
- 2094 ft AGL at event
- 161 kt ground speed
- 0 fpm vertical
- Approach stability 45/100
- 7 kt wind
- 4 kt crosswind component
- 3,219 m visibility
- KPTK 131353Z COR 34009KT 2SM -RASN BR BKN006 OVC011 02/01 A2989 RMK AO2 SFC VIS 8 SLP130 P0000 T00170006
Flight context
- RAX285
- Royal AIR Freight
- FA20
- KSNA → KPTK
- 2026-05-25 23:50 UTC
- KPTK runway 27L
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