AFR334M was operating from LFPG to KBOS on 2026-07-10. SkyMeter detected a go-around at General Edward Lawrence Logan International Airport (KBOS) on runway 33L at 19:01 UTC. Trace data at the event: 150 ft AGL, 160 kt GS, 0 fpm vertical. METAR at the time reported 3 kt wind, 3 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/3959 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Boston, MA, Monday, June 1, 2026 through Monday, July 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 → - AIR SHOWS/SPORTS6/2697 2026-07-09 16:00Z – 2026-07-12 21:00Z SFC–15,000 ft
Brunswick, ME, Thursday, July 9, 2026 through Sunday, July 12, 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
- Runway 33L
- 150 ft AGL at event
- 160 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KBOS 170754Z 18005KT 10SM FEW055 SCT080 19/17 A3026 RMK AO2 SLP246 T01940172
Flight context
- AFR334M
- A332
- LFPG → KBOS
- 2026-07-10 19:01 UTC
- KBOS runway 33L
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