Stall warning — UAE2VL

2026-08-03 15:46 UTC· KIAH OMDB· A388

UAE2VL was operating from KIAH to OMDB on 2026-08-03. SkyMeter detected a stall warning at 15:46 UTC. Trace data at the event: 2358 ft AGL, 108 kt GS. METAR at the time reported 8 kt wind, 2 kt crosswind component. A stall flag is raised when the inferred angle of attack and observed airspeed are consistent with a stalled wing. Stall events on general-aviation trainer aircraft are predominantly stall-recognition practice during primary flight training, not safety-of-flight incidents. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • 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/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

    NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/2790 2026-07-02 22:30Z – 2026-09-15 03:59Z SFC–400 ft

    St. George, ME, Thursday, July 2, 2026 through Monday, September 14, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft

    2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/8900 2026-07-30 10:00Z – 2026-08-03 23:59Z SFC–400 ft

    DETROIT, MI, Thursday, July 30, 2026 through Monday, August 3, 2026 Local

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/8930 2026-07-30 16:00Z – 2026-08-03 03:00Z SFC–400 ft

    Chicago, IL, Thursday, July 30, 2026 through Monday, August 3, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/8923 2026-07-30 21:00Z – 2026-08-10 03:59Z SFC–400 ft

    Bethlehem, PA, Thursday, July 30, 2026 through Sunday, August 9, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/0628 2026-07-31 13:07Z – 2026-08-03 01:30Z SFC–1,300 ft

    13NM S TAYLOR, FL, Friday, July 31, 2026 through Monday, August 3, 2026 UTC

    View FAA NOTAM →
  • VIP6/0568 2026-07-31 19:00Z – 2026-08-03 22:30Z SFC–4,999 ft

    Middleburg, VA, Friday, July 31, 2026 through Monday, August 3, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

    Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

    View FAA NOTAM →
  • SECURITY6/0028 2026-08-01 19:00Z – 2026-08-03 03:59Z SFC–400 ft

    East Rutherford, NJ, Saturday, August 1, 2026 through Sunday, August 2, 2026 Local

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/8932 2026-08-02 12:00Z – 2026-08-03 05:00Z SFC–400 ft

    st louis, MO, Sunday, August 2, 2026 through Monday, August 3, 2026 UTC

    View FAA NOTAM →
  • VIP6/0992 2026-08-02 21:45Z – 2026-08-03 23:45Z SFC–4,999 ft

    Middleburg, VA, Sunday, August 2, 2026 through Monday, August 3, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0929 2026-08-03 12:30Z – 2026-08-08 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, August 3, 2026 through Saturday, August 8, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/0663 2026-08-03 13:00Z – 2026-08-03 22:00Z SFC–2,000 ft

    SEDALIA, MO, Monday, August 3, 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

  • 2358 ft AGL at event
  • 108 kt ground speed
  • 0 fpm vertical
  • 8 kt wind
  • 2 kt crosswind component

Flight context

  • UAE2VL
  • A388
  • KIAH → OMDB
  • 2026-08-03 15:46 UTC

All events on this flight

Stall warning 15:46:30 UTC · · 2,358 ft AGL · 108 kt GS
Stall warning 15:46:30 UTC · · 2,358 ft AGL · 108 kt GS

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