Unstable approach — JPR45

JPR45 (Usda Forest Service Fire & Aviation) was operating from KALW to KRDM on 2026-08-28. SkyMeter detected a low approach-stability score at Roberts Field (KRDM) on runway 23 at 03:32 UTC. Trace data at the event: 4141 ft AGL, 132 kt GS. Approach stability score: 25/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, 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/4957 2026-08-13 17:30Z – 2026-08-28 04:00Z SFC–10,500 ft

  18NM NW JOHN DAY, OR, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5112 2026-08-14 16:30Z – 2026-08-29 03:00Z SFC–9,500 ft

  19NM NW JOHN DAY, OR, Friday, August 14, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5190 2026-08-15 04:00Z – 2026-08-29 04:00Z SFC–10,500 ft

  20NM SW THE DALLES, OR, Saturday, August 15, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5212 2026-08-15 15:00Z – 2026-08-30 04:00Z SFC–9,500 ft

  19NM NW JOHN DAY, OR, Saturday, August 15, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6726 2026-08-20 03:15Z – 2026-09-03 04:00Z SFC–9,000 ft

  25NM E PENDLETON, OR, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC

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

  12NM NE PRINEVILLE, OR, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7123 2026-08-23 14:00Z – 2026-09-05 04:00Z SFC–12,500 ft

  18NM W BAKER CITY, OR, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7124 2026-08-23 14:00Z – 2026-09-05 04:00Z SFC–12,500 ft

  18NM W BAKER CITY, OR, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7285 2026-08-23 18:00Z – 2026-09-06 04:00Z SFC–8,500 ft

  GRANDVIEW, WA, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

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

  37NM NE PRINEVILLE, OR, Tuesday, August 25, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7653 2026-08-25 03:00Z – 2026-09-08 04:00Z SFC–10,500 ft

  20NM SW THE DALLES, OR, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8093 2026-08-26 03:30Z – 2026-09-09 04:00Z SFC–9,000 ft

  25NM E PENDLETON, OR, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

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

  17NM W BAKER CITY, OR, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

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

  17NM W BAKER CITY, OR, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/6918 2026-08-27 20:30Z – 2026-08-29 23:59Z SFC–15,500 ft

  MADRAS, OR, Thursday, August 27, 2026 through Saturday, August 29, 2026 Local

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

  37NM NE PRINEVILLE, OR, Friday, August 28, 2026 through Monday, August 31, 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