Go-around — EDV5418

EDV5418 (Delta AIR Lines) was operating from KATL to KCHO on 2026-07-13. SkyMeter detected a go-around at Charlottesville Albemarle Airport (KCHO) on runway 03 at 15:36 UTC. Trace data at the event: 1651 ft AGL, 148 kt GS. METAR at the time reported 5 kt wind, 4 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.

• SECURITY6/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  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/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/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Charlotte, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 2026 Local

  View FAA NOTAM →
• SECURITY6/7169 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft

  White Sulphur Springs, WV

  View FAA NOTAM →
• SECURITY6/7594 2026-07-08 16:07Z – 2026-07-21 03:59Z SFC–400 ft

  Atlanta, GA

  View FAA NOTAM →
• SECURITY6/7597 2026-07-08 16:07Z – 2026-07-21 03:59Z SFC–400 ft

  Marietta, GA

  View FAA NOTAM →
• SECURITY6/7564 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft

  Conway, SC

  View FAA NOTAM →
• SECURITY6/3224 2026-07-11 04:01Z – 2026-07-15 03:59Z SFC–1,000 ft

  Atlanta, GA, Saturday, July 11, 2026 through Tuesday, July 14, 2026 Local

  View FAA NOTAM →
• HAZARDS6/4931 2026-07-11 15:58Z – 2026-07-23 01:00Z SFC–3,000 ft

  2NM NE SHALLOTTE, NC, Saturday, July 11, 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