Unstable approach — N307HR

N307HR (Seminole Tribe of Florida DBA) was operating from KFLL to KLAS on 2026-07-23. SkyMeter detected a low approach-stability score at McCarran International Airport (KLAS) on runway 19R at 17:21 UTC. Trace data at the event: 3281 ft AGL, 152 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 3 kt wind, 3 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.

• SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft

  South Padre Island, TX, Tuesday, May 6, 2025 Local

  View FAA NOTAM →
• SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

  Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft

  Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

  View FAA NOTAM →
• SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

  SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• HAZARDS6/6155 2026-07-16 16:00Z – 2026-07-23 23:00Z SFC–1,500 ft

  0NM W INGRAM, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6156 2026-07-16 16:09Z – 2026-07-23 23:00Z SFC–1,500 ft

  1NM SE KERRVILLE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6157 2026-07-16 16:15Z – 2026-07-23 23:00Z SFC–1,500 ft

  1NM NW BOERNE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6158 2026-07-16 16:23Z – 2026-07-23 23:00Z SFC–1,500 ft

  3NM SW UVALDE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6217 2026-07-16 18:17Z – 2026-07-23 23:00Z SFC–1,500 ft

  1NM W INGRAM, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6218 2026-07-16 18:17Z – 2026-07-23 23:00Z SFC–1,500 ft

  1NM SE KERRVILLE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6186 2026-07-17 13:00Z – 2026-07-30 03:00Z SFC–11,000 ft

  21NM NE DOUGLAS, AZ, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6528 2026-07-17 19:40Z – 2026-07-24 05:00Z SFC–1,500 ft

  CRYSTAL CITY, TX, Friday, July 17, 2026 through Friday, July 24, 2026 UTC

  View FAA NOTAM →
• SECURITY6/6747 2026-07-20 12:30Z – 2026-07-24 06:00Z SFC–2,500 ft

  MAYPORT, FL, Monday, July 20, 2026 through Friday, July 24, 2026 Local

  View FAA NOTAM →
• HAZARDS6/7482 2026-07-21 18:00Z – 2026-07-23 18:00Z SFC–1,500 ft

  TILDEN, TX, Tuesday, July 21, 2026 through Thursday, July 23, 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