Go-around — JBU772
KBOS · 272025-11-17 01:22 UTC· MMUN → KBOS· JETBLUE AIRWAYS CORP· A321
JBU772 (Jetblue Airways) was operating from MMUN to KBOS on 2025-11-17. SkyMeter detected a go-around at General Edward Lawrence Logan International Airport (KBOS) on runway 27 at 01:22 UTC. Trace data at the event: 227 ft AGL, 152 kt GS, 0 fpm vertical. METAR at the time reported 14 kt wind, 5 kt crosswind component, 4,828 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - 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 →
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 27
- 227 ft AGL at event
- 152 kt ground speed
- 0 fpm vertical
- 14 kt wind
- 5 kt crosswind component
- 4,828 m visibility
- METAR KBOS 261254Z 03027G37KT 3SM -RA BR FEW023 OVC031 13/12 A2993 RMK AO2 PK WND 03037/1254 SLP135 P0002 T01330117
Flight context
- JBU772
- Jetblue Airways
- A321
- MMUN → KBOS
- 2025-11-17 01:22 UTC
- KBOS runway 27
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