Unstable approach — RAX123

RAX123 (Royal AIR Freight) was operating from KSAT to KPTK on 2026-08-21. SkyMeter detected a low approach-stability score at Oakland County International Airport (KPTK) on runway 09L at 06:57 UTC. Trace data at the event: 2096 ft AGL, 151 kt GS. METAR at the time reported 5 kt wind, 2 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.

• SECURITY6/4348 2026-03-08 07:00Z – 2026-11-01 06:59Z SFC–2,400 ft

  GRAND FORKS AFB, ND, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

  SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

  Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

  View FAA NOTAM →
• HAZARDS6/1462 2026-08-04 13:00Z – 2026-09-01 04:00Z SFC–15,000 ft

  20NM SW PUEBLO, CO, Tuesday, August 4, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2899 2026-08-08 10:00Z – 2026-08-22 02:00Z SFC–7,000 ft

  13NM N ELY, MN, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3075 2026-08-08 19:30Z – 2026-08-22 04:00Z SFC–12,000 ft

  28NM NE LAS VEGAS, NM, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3101 2026-08-09 13:00Z – 2026-08-24 03:00Z SFC–15,000 ft

  24NM SW PUEBLO, CO, Sunday, August 9, 2026 through Monday, August 24, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/2574 2026-08-13 12:00Z – 2026-08-24 05:00Z SFC–400 ft

  des moines, IA, Thursday, August 13, 2026 through Monday, August 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4893 2026-08-13 13:00Z – 2026-08-28 03:00Z SFC–9,000 ft

  43NM E HOT SPRINGS, SD, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4894 2026-08-13 13:00Z – 2026-08-28 04:00Z SFC–15,000 ft

  8NM SE TRINIDAD, CO, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft

  Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• SECURITY6/3628 2026-08-17 12:00Z – 2026-08-23 23:59Z SFC–400 ft

  SAINT LOUIS, MO, Monday, August 17, 2026 through Sunday, August 23, 2026 Local

  View FAA NOTAM →
• HAZARDS6/6589 2026-08-20 10:00Z – 2026-09-02 02:00Z SFC–5,500 ft

  13NM N ELY, MN, Thursday, August 20, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6625 2026-08-20 10:00Z – 2026-09-02 02:00Z SFC–5,500 ft

  13NM N ELY, MN, Thursday, August 20, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• VIP6/5889 2026-08-20 21:15Z – 2026-08-23 21:15Z SFC–4,999 ft

  Cincinnati, OH, Thursday, August 20, 2026 through Sunday, August 23, 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.

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