Unstable approach — N43LJ

N43LJ (MRP Texas) was operating from KTIW to KPIR on 2026-07-17. SkyMeter detected a low approach-stability score at Pierre Regional Airport (KPIR) on runway 31 at 17:45 UTC. Trace data at the event: 2823 ft AGL, 172 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 6 kt wind, 5 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/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4040 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Portland, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4041 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  PORTLAND, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/2989 2026-07-05 17:35Z – 2026-07-20 05:00Z SFC–7,000 ft

  15NM E PENDLETON, OR, Sunday, July 5, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3022 2026-07-06 14:00Z – 2026-07-20 05:00Z SFC–8,000 ft

  15NM E PENDLETON, OR, Monday, July 6, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• SECURITY6/8071 2026-07-08 16:07Z – 2026-07-21 06:59Z SFC–400 ft

  PORTLAND, OR

  View FAA NOTAM →
• HAZARDS6/4238 2026-07-09 13:00Z – 2026-07-23 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4242 2026-07-09 13:00Z – 2026-07-23 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4239 2026-07-09 14:00Z – 2026-07-23 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4241 2026-07-09 14:00Z – 2026-07-23 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4548 2026-07-10 14:00Z – 2026-07-24 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Friday, July 10, 2026 through Friday, July 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4549 2026-07-10 14:00Z – 2026-07-24 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Friday, July 10, 2026 through Friday, July 24, 2026 UTC

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

  35NM E LEWISTON, ID, Saturday, July 11, 2026 through Saturday, July 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4954 2026-07-11 20:52Z – 2026-07-19 05:00Z SFC–8,500 ft

  7NM S WENATCHEE, WA, Saturday, July 11, 2026 through Sunday, July 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4970 2026-07-12 15:00Z – 2026-07-27 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Sunday, July 12, 2026 through Monday, July 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4968 2026-07-12 15:00Z – 2026-07-27 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Sunday, July 12, 2026 through Monday, July 27, 2026 UTC

  View FAA NOTAM →
• SECURITY6/8074 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft

  Renton, WA

  View FAA NOTAM →
• HAZARDS6/5879 2026-07-15 14:00Z – 2026-07-28 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Wednesday, July 15, 2026 through Tuesday, July 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5880 2026-07-15 14:00Z – 2026-07-29 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Wednesday, July 15, 2026 through Wednesday, July 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6101 2026-07-16 04:05Z – 2026-07-23 04:00Z SFC–8,000 ft

  18NM W SPRAY, OR, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6151 2026-07-16 15:28Z – 2026-07-30 04:00Z SFC–8,000 ft

  18NM W SPRAY, OR, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6314 2026-07-16 21:42Z – 2026-07-31 04:00Z SFC–8,500 ft

  12NM NW CLE ELUM, WA, Thursday, July 16, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6401 2026-07-17 04:01Z – 2026-07-31 04:00Z SFC–8,500 ft

  12NM NW CLE ELUM, WA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6408 2026-07-17 04:31Z – 2026-07-31 04:00Z SFC–9,000 ft

  10NM SW CULVER, OR, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• 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 →

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