N773MB (MB Ramble ON) was operating from MWCR to KSTL on 2026-06-06. SkyMeter detected a stall warning at 13:02 UTC. Trace data at the event: 702 ft AGL, 165 kt GS. Approach stability score: 83/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 13 kt wind, 13 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)- SECURITY6/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft
Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 2026 Local
View FAA NOTAM → - HAZARDS6/3292 2026-05-27 17:20Z – 2026-06-10 00:15Z SFC–2,000 ft
22NM SW TALLAHASSEE, FL, Wednesday, May 27, 2026 through Wednesday, June 10, 2026 UTC
View FAA NOTAM → - SECURITY6/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3980 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3990 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3991 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3998 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Atlanta, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, 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/4119 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4121 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4135 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4161 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/5656 2026-06-04 16:19Z – 2026-06-18 00:15Z SFC–2,000 ft
22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC
View FAA NOTAM → - HAZARDS6/5771 2026-06-04 21:47Z – 2026-06-18 00:15Z SFC–3,500 ft
22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 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
- 702 ft AGL at event
- 165 kt ground speed
- 0 fpm vertical
- Approach stability 83/100
- 13 kt wind
- 13 kt crosswind component
Flight context
- N773MB
- MB Ramble ON
- G280
- MWCR → KSTL
- 2026-06-06 13:02 UTC
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