Unstable approach — N178AS

N178AS (Alpha Sierra Aviation) was operating from KFCM to KPSP on 2026-08-24. SkyMeter detected a low approach-stability score at Palm Springs International Airport (KPSP) on runway 13R at 22:24 UTC. Trace data at the event: 1592 ft AGL, 151 kt GS. Approach stability score: 34/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, 7 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.

• 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/3161 2026-08-10 12:00Z – 2026-08-25 03:30Z SFC–16,000 ft

  13NM SE LANDER, WY, Monday, August 10, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3679 2026-08-11 12:00Z – 2026-08-25 08:00Z SFC–16,500 ft

  1NM NE OURAY, CO, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3712 2026-08-11 14:00Z – 2026-08-25 04:00Z SFC–8,000 ft

  18NM SW PRESCOTT, AZ, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4085 2026-08-12 04:00Z – 2026-08-25 04:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Wednesday, August 12, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4111 2026-08-12 05:00Z – 2026-08-27 05:00Z SFC–10,000 ft

  104NM SE BURNS, OR, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4089 2026-08-12 12:00Z – 2026-08-27 03:30Z SFC–15,000 ft

  2NM SE LANDER, WY, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4363 2026-08-12 17:00Z – 2026-08-26 04:00Z SFC–12,500 ft

  33NM N BOISE, ID, Wednesday, August 12, 2026 through Wednesday, August 26, 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 →
• HAZARDS6/4727 2026-08-13 14:00Z – 2026-08-27 04:00Z SFC–12,500 ft

  33NM N BOISE, ID, Thursday, August 13, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5073 2026-08-14 14:00Z – 2026-08-28 04:00Z SFC–12,500 ft

  33NM N BOISE, ID, Friday, August 14, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5409 2026-08-17 04:00Z – 2026-08-30 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5463 2026-08-17 13:00Z – 2026-08-30 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5937 2026-08-18 13:00Z – 2026-08-31 03:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6216 2026-08-19 03:00Z – 2026-09-02 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Wednesday, August 19, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6728 2026-08-20 13:00Z – 2026-08-27 03:00Z SFC–14,500 ft

  8NM N ASPEN, CO, Thursday, August 20, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6724 2026-08-20 13:00Z – 2026-09-03 03:30Z SFC–11,500 ft

  32NM NE BOISE, ID, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6954 2026-08-21 14:00Z – 2026-09-04 03:00Z SFC–11,000 ft

  33NM SW POCATELLO, ID, Friday, August 21, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7092 2026-08-22 13:00Z – 2026-09-04 03:00Z SFC–14,000 ft

  26NM SW PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7115 2026-08-22 23:30Z – 2026-09-04 03:00Z SFC–13,000 ft

  41NM E PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7121 2026-08-23 03:30Z – 2026-09-05 04:00Z SFC–10,000 ft

  60NM SW MOUNTAIN HOME, ID, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7117 2026-08-23 11:00Z – 2026-08-29 01:00Z SFC–13,500 ft

  30NM SW PUEBLO, CO, Sunday, August 23, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7347 2026-08-24 13:00Z – 2026-09-07 04:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7530 2026-08-24 17:00Z – 2026-09-06 03:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Sunday, September 6, 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