Unstable approach — 5626PT

5626PT (KBC Aviation) was inbound to KHOU on 2026-06-26. SkyMeter detected a low approach-stability score at William P Hobby Airport (KHOU) on runway 13R at 21:45 UTC. Trace data at the event: 1135 ft AGL, 181 kt GS. Approach stability score: 60/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 13 kt wind, 8 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/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 →
• SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

  OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

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

  BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Miami, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  TAMPA, FL, 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/7228 2026-06-13 04:01Z – 2026-07-06 03:59Z SFC–1,000 ft

  Miami, FL, Saturday, June 13, 2026 through Sunday, July 5, 2026 Local

  View FAA NOTAM →
• SECURITY6/0299 2026-06-26 04:00Z – 2026-10-18 03:59Z SFC–5,000 ft

  Key West, FL, Friday, June 26, 2026 through Saturday, October 17, 2026 Local

  View FAA NOTAM →
• SECURITY6/0777 2026-06-26 04:01Z – 2026-07-21 03:59Z SFC–400 ft

  Fort Lauderdale, FL, Friday, June 26, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/0782 2026-06-26 04:01Z – 2026-07-21 03:59Z SFC–400 ft

  Fort Lauderdale, FL, Friday, June 26, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/0794 2026-06-26 14:00Z – 2026-06-26 18:00Z SFC–1,000 ft

  BOCA RATON, FL, Friday, June 26, 2026 UTC

  View FAA NOTAM →
• SECURITY6/9594 2026-06-26 21:00Z – 2026-06-27 06:00Z SFC–3,000 ft

  Houston, TX, Friday, June 26, 2026 through Saturday, June 27, 2026 Local

  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