Unstable approach — N586DM
KFFZ · 22L2026-07-04 20:44 UTC· KCCR → KFFZ· MAC EQUIPMENT LEASING LLC· G280
N586DM (MAC Equipment Leasing) was operating from KCCR to KFFZ on 2026-07-04. SkyMeter detected a low approach-stability score at Falcon Field (KFFZ) on runway 22L at 20:44 UTC. Trace data at the event: 2504 ft AGL, 132 kt GS. Approach stability score: 37/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 4 kt wind, 4 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4204 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
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/4052 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4054 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4182 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4189 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4192 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4197 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
GOLETA, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4198 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
IRVINE, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4201 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Dana Point, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7265 2026-06-12 21:07Z – 2026-07-16 06:29Z SFC–400 ft
Manhattan Beach, CA
View FAA NOTAM → - HAZARDS6/0842 2026-06-26 14:00Z – 2026-07-09 03:00Z SFC–10,500 ft
13NM SW FLAGSTAFF, AZ, Friday, June 26, 2026 through Thursday, July 9, 2026 UTC
View FAA NOTAM → - SECURITY6/7842 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Montecito, CA
View FAA NOTAM → - SECURITY6/7078 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ
View FAA NOTAM → - HAZARDS6/1244 2026-06-28 21:00Z – 2026-07-12 04:00Z SFC–10,500 ft
13NM SW FLAGSTAFF, AZ, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/1322 2026-06-29 03:00Z – 2026-07-13 16:00Z SFC–10,500 ft
13NM SW FLAGSTAFF, AZ, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - SECURITY6/7841 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft
Goleta, CA
View FAA NOTAM → - HAZARDS6/1323 2026-06-29 16:00Z – 2026-07-13 03:00Z SFC–10,500 ft
13NM SW FLAGSTAFF, AZ, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1728 2026-06-30 03:00Z – 2026-07-13 16:00Z SFC–8,500 ft
13NM SW FLAGSTAFF, AZ, Tuesday, June 30, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/2594 2026-07-02 13:00Z – 2026-07-15 04:00Z SFC–12,000 ft
23NM S PANACA, NV, Thursday, July 2, 2026 through Wednesday, July 15, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/0753 2026-07-02 14:00Z – 2026-07-06 04:00Z SFC–400 ft
Los Angeles, CA, Thursday, July 2, 2026 through Monday, July 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/2595 2026-07-02 14:00Z – 2026-07-13 05:00Z SFC–12,000 ft
12NM N PIOCHE, NV, Thursday, July 2, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/2593 2026-07-02 14:00Z – 2026-07-13 05:00Z SFC–12,000 ft
12NM N PIOCHE, NV, Thursday, July 2, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/2561 2026-07-02 16:00Z – 2026-07-15 03:00Z SFC–12,000 ft
13NM SW FLAGSTAFF, AZ, Thursday, July 2, 2026 through Wednesday, July 15, 2026 UTC
View FAA NOTAM → - SECURITY6/7843 2026-07-03 16:07Z – 2026-07-21 06:59Z SFC–400 ft
Santa Barbara, CA
View FAA NOTAM → - SECURITY6/7847 2026-07-03 16:07Z – 2026-07-21 06:59Z SFC–400 ft
Santa Barbara, CA
View FAA NOTAM → - UAS PUBLIC GATHERING6/1486 2026-07-04 14:00Z – 2026-07-06 04:00Z SFC–400 ft
Los Angeles, CA, Saturday, July 4, 2026 through Monday, July 6, 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.
Pilot review data
- Runway 22L
- 2504 ft AGL at event
- 132 kt ground speed
- 0 fpm vertical
- Approach stability 37/100
- 4 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- METAR KFFZ 161154Z AUTO 13006KT 10SM CLR 29/17 A2992 RMK AO2 SLP104 T02890167 10311 20289 50001
Flight context
- N586DM
- MAC Equipment Leasing
- G280
- KCCR → KFFZ
- 2026-07-04 20:44 UTC
- KFFZ runway 22L
All events on this flight
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