Unstable approach — JPR14

JPR14 (Usda Forest Service Fire & Aviation) was operating from KRDM to KYKM on 2026-07-30. SkyMeter detected a low approach-stability score at Yakima Air Terminal McAllister Field (KYKM) on runway 27 at 17:16 UTC. Trace data at the event: 2166 ft AGL, 132 kt GS. Approach stability score: 43/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/6458 2026-07-17 15:40Z – 2026-08-01 04:00Z SFC–9,000 ft

  9NM E MADRAS, OR, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6695 2026-07-18 20:09Z – 2026-07-31 04:00Z SFC–9,000 ft

  12NM SE MADRAS, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6734 2026-07-19 01:25Z – 2026-08-01 04:00Z SFC–9,000 ft

  26NM E MADRAS, OR, Sunday, July 19, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6757 2026-07-19 16:07Z – 2026-08-02 04:00Z SFC–9,000 ft

  12NM SE MADRAS, OR, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6778 2026-07-19 19:09Z – 2026-08-03 03:00Z SFC–8,000 ft

  1NM S FOSSIL, OR, Sunday, July 19, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7177 2026-07-20 22:03Z – 2026-08-04 04:00Z SFC–8,000 ft

  1NM W CONDON, OR, Monday, July 20, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7611 2026-07-22 03:41Z – 2026-08-05 04:00Z SFC–8,000 ft

  1NM S FOSSIL, OR, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

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

  26NM E MADRAS, OR, Wednesday, July 22, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8355 2026-07-24 14:00Z – 2026-08-07 04:00Z SFC–9,000 ft

  26NM E MADRAS, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8357 2026-07-24 14:00Z – 2026-08-07 04:00Z SFC–9,000 ft

  12NM SE MADRAS, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8479 2026-07-24 20:30Z – 2026-08-08 04:00Z SFC–8,000 ft

  34NM SE THE DALLES, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8488 2026-07-25 01:30Z – 2026-08-08 05:00Z SFC–8,000 ft

  32NM NE MADRAS, OR, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8545 2026-07-25 17:00Z – 2026-08-09 04:00Z SFC–7,000 ft

  8NM SW THE DALLES, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8550 2026-07-25 18:00Z – 2026-08-09 05:00Z SFC–8,000 ft

  32NM NE MADRAS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8555 2026-07-25 19:00Z – 2026-08-09 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8565 2026-07-25 22:00Z – 2026-08-09 05:00Z SFC–9,000 ft

  20NM SE MADRAS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8581 2026-07-26 05:00Z – 2026-08-09 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8859 2026-07-26 22:00Z – 2026-08-10 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8861 2026-07-26 22:45Z – 2026-08-10 05:00Z SFC–8,000 ft

  32NM NE MADRAS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9350 2026-07-27 22:00Z – 2026-08-11 22:00Z SFC–9,000 ft

  20NM SE MADRAS, OR, Monday, July 27, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9561 2026-07-28 16:45Z – 2026-08-11 04:00Z SFC–8,000 ft

  32NM NE MADRAS, OR, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9804 2026-07-28 22:00Z – 2026-08-11 04:00Z SFC–8,000 ft

  4NM S FOSSIL, OR, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9939 2026-07-29 14:00Z – 2026-08-12 04:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0415 2026-07-30 15:00Z – 2026-08-12 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Thursday, July 30, 2026 through Wednesday, August 12, 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