Unstable approach — N513TM

N513TM (7 Romeo Bravo) was operating from KUAO to KRNO on 2026-09-04. SkyMeter detected a low approach-stability score at Reno Tahoe International Airport (KRNO) on runway 17L at 23:45 UTC. Trace data at the event: 4993 ft AGL, 104 kt GS. Approach stability score: 38/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 15 kt wind, 10 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/7113 2026-08-22 20:30Z – 2026-09-05 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Saturday, August 22, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7127 2026-08-23 05:30Z – 2026-09-06 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7283 2026-08-23 16:00Z – 2026-09-06 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7609 2026-08-24 23:37Z – 2026-09-07 03:00Z SFC–8,000 ft

  15NM NE ALTURAS, CA, Monday, August 24, 2026 through Monday, September 7, 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/7708 2026-08-25 13:13Z – 2026-09-08 03:00Z SFC–8,000 ft

  15NM NE ALTURAS, CA, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7989 2026-08-25 22:30Z – 2026-09-08 03:00Z SFC–11,000 ft

  14NM NE CEDARVILLE, CA, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

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

  14NM E CEDARVILLE, CA, Wednesday, August 26, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9246 2026-08-31 03:30Z – 2026-09-15 13:00Z SFC–10,500 ft

  20NM SW THE DALLES, OR, Monday, August 31, 2026 through Tuesday, September 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9247 2026-08-31 03:30Z – 2026-09-15 04:00Z SFC–10,500 ft

  40NM SE PORTLAND, OR, Monday, August 31, 2026 through Tuesday, September 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9248 2026-08-31 04:00Z – 2026-09-15 13:00Z SFC–10,500 ft

  41NM SE PORTLAND, OR, Monday, August 31, 2026 through Tuesday, September 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9463 2026-08-31 18:37Z – 2026-09-16 04:00Z SFC–9,000 ft

  12NM NE PRINEVILLE, OR, Monday, August 31, 2026 through Wednesday, September 16, 2026 UTC

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

  14NM N OAKRIDGE, OR, Tuesday, September 1, 2026 through Tuesday, September 15, 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