Unstable approach — JRE785

K52F · 17

2026-07-18 01:37 UTC· FE CJ3 274 LLC· C25B

JRE785 (FE CJ3 274) was inbound to K52F on 2026-07-18. SkyMeter detected a low approach-stability score at Northwest Regional Airport (K52F) on runway 17 at 01:37 UTC. Trace data at the event: 1734 ft AGL, 104 kt GS. Approach stability score: 42/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, 2 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/3705 2026-05-29 05:00Z – 2026-07-20 08:00Z SFC–400 ft

    DALLAS, TX, Friday, May 29, 2026 through Monday, July 20, 2026 Local

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

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

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

    MANSFIELD, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

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

    View FAA NOTAM →
  • 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/6840 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft

    Mansfield, TX

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

    Fort Worth, TX

    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 →
  • SECURITY6/4573 2026-07-14 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft

    Dallas, TX, Tuesday, July 14, 2026 through Sunday, July 19, 2026 Local

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

    Irving, TX

    View FAA NOTAM →
  • SECURITY6/6839 2026-07-17 23:07Z – 2026-07-21 04:59Z SFC–400 ft

    Arlington, 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.

Pilot review data

  • Runway 17
  • 1734 ft AGL at event
  • 104 kt ground speed
  • 0 fpm vertical
  • Approach stability 42/100
  • 6 kt wind
  • 2 kt crosswind component

Flight context

  • JRE785
  • FE CJ3 274
  • C25B
  • 2026-07-18 01:37 UTC
  • K52F runway 17

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

SkyMeter · trace data observed via ADS-B· K52F