AFR33J was operating from KATL to LFPG on 2026-05-22. SkyMeter detected a go-around at Charles de Gaulle International Airport (LFPG) on runway 08R at 07:58 UTC. Trace data at the event: 777 ft AGL, 160 kt GS. METAR at the time reported 2 kt wind, 2 kt crosswind component, 9,994 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft
Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local
View FAA NOTAM → - SECURITY6/1954 2026-05-21 12:00Z – 2026-05-22 21:00Z SFC–1,000 ft
Foxborough, MA, Thursday, May 21, 2026 through Friday, May 22, 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.
Pilot review data
- Runway 08R
- 777 ft AGL at event
- 160 kt ground speed
- 0 fpm vertical
- 2 kt wind
- 2 kt crosswind component
- 9,994 m visibility
- LFPG 200300Z 23004KT CAVOK 16/13 Q1024 NOSIG
Flight context
- AFR33J
- B789
- KATL → LFPG
- 2026-05-22 07:58 UTC
- LFPG runway 08R
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