Unstable approach — N424JR

N424JR (Gravitas Aviation) was operating from 84TS to KLNC on 2026-07-09. SkyMeter detected a low approach-stability score at Dallas Executive Airport (KRBD) on runway 13 at 19:12 UTC. Trace data at the event: 1750 ft AGL, 170 kt GS. Approach stability score: 70/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 11 kt wind, 6 kt crosswind component. 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/4059 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/6447 2026-06-09 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft

  Houston, TX, Tuesday, June 9, 2026 through Sunday, July 19, 2026 Local

  View FAA NOTAM →
• SECURITY6/6787 2026-07-03 15:07Z – 2026-07-21 04:59Z SFC–400 ft

  Houston, TX

  View FAA NOTAM →
• SECURITY6/6783 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Houston, TX

  View FAA NOTAM →
• SECURITY6/6838 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

  Houston, TX

  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