N86TG had departed KEDC on 2026-03-14. SkyMeter detected a rejectedtakeoff at Austin Executive Airport (KEDC) on runway 13 at 19:15 UTC. Trace data at the event: 620 ft AGL, 76 kt GS. METAR at the time reported 11 kt wind, 8 kt crosswind component, 12,875 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 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.
Pilot review data
- Runway 13
- 620 ft AGL at event
- 76 kt ground speed
- 0 fpm vertical
- 11 kt wind
- 8 kt crosswind component
- 12,875 m visibility
- METAR KEDC 160355Z AUTO 17008KT 140V210 8SM CLR 30/22 A3008 RMK AO2 T02960217 $
Flight context
- N86TG
- C25A
- 2026-03-14 19:15 UTC
- KEDC runway 13
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