Unstable approach — N484JC

N484JC (Whitefish Investment Partners) was operating from KSDL to KDAL on 2026-06-28. SkyMeter detected a low approach-stability score at Dallas Love Field (KDAL) on runway 13L at 17:58 UTC. Trace data at the event: 1579 ft AGL, 189 kt GS. Approach stability score: 58/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 16 kt wind, 9 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/4008 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

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

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

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

  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/4025 2026-06-01 05:00Z – 2026-07-21 04:59Z

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

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

  MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/9123 2026-06-18 12:00Z – 2026-06-30 05:00Z SFC–14,000 ft

  80NM N SILVER CITY, NM, Thursday, June 18, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9125 2026-06-18 14:00Z – 2026-07-02 04:00Z SFC–10,000 ft

  45NM E MESA, AZ, Thursday, June 18, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9342 2026-06-20 00:21Z – 2026-07-02 04:00Z SFC–13,500 ft

  30NM N SILVER CITY, NM, Saturday, June 20, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9420 2026-06-20 21:25Z – 2026-07-04 04:00Z SFC–12,000 ft

  40NM SE ALBUQUERQUE, NM, Saturday, June 20, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9456 2026-06-21 13:00Z – 2026-07-05 04:00Z SFC–12,000 ft

  40NM SE ALBUQUERQUE, NM, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9455 2026-06-21 14:00Z – 2026-07-05 04:00Z SFC–9,000 ft

  14NM E PAYSON, AZ, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9496 2026-06-21 14:00Z – 2026-07-05 03:00Z SFC–13,000 ft

  33NM W SHOW LOW, AZ, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9548 2026-06-22 14:00Z – 2026-07-05 04:00Z SFC–10,000 ft

  16NM NE SAN CARLOS, AZ, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9854 2026-06-23 14:00Z – 2026-07-06 04:00Z SFC–10,000 ft

  45NM E MESA, AZ, Tuesday, June 23, 2026 through Monday, July 6, 2026 UTC

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

  Mesa, AZ

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

  Mesa, AZ

  View FAA NOTAM →
• HAZARDS6/1096 2026-06-28 14:00Z – 2026-07-11 04:00Z SFC–9,000 ft

  16NM S GLOBE, AZ, Sunday, June 28, 2026 through Saturday, July 11, 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