Go-around — RPA3568
KEWR · 292025-10-20 18:29 UTC· CYQB → KEWR· REPUBLIC AIRWAYS INC· E75L
RPA3568 (Republic Airways) was operating from CYQB to KEWR on 2025-10-20. SkyMeter detected a go-around at Newark Liberty International Airport (KEWR) on runway 29 at 18:29 UTC. Trace data at the event: 204 ft AGL, 135 kt GS, 0 fpm vertical. Approach stability score: 85/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 16 kt wind, 1 kt crosswind component. 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 →
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 29
- 204 ft AGL at event
- 135 kt ground speed
- 0 fpm vertical
- Approach stability 85/100
- 16 kt wind
- 1 kt crosswind component
- METAR KEWR 271451Z 03018G28KT 1 1/2SM -RA BR BKN008 OVC015 17/16 A2960 RMK AO2 PK WND 02034/1404 SLP022 P0001 60004 T01670156 53030 $
Flight context
- RPA3568
- Republic Airways
- E75L
- CYQB → KEWR
- 2025-10-20 18:29 UTC
- KEWR runway 29
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