Go-around — RPA3627
KPWM · 112026-09-04 04:02 UTC· KEWR → KPWM· REPUBLIC AIRWAYS INC· E75L
RPA3627 (Republic Airways) was operating from KEWR to KPWM on 2026-09-04. SkyMeter detected a go-around at Portland International Jetport (KPWM) on runway 11 at 04:02 UTC. Trace data at the event: 446 ft AGL, 156 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 2 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)- 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/7002 2026-08-24 13:00Z – 2026-09-13 07:00Z SFC–1,000 ft
Flushing, NY, Monday, August 24, 2026 through Sunday, September 13, 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 11
- 446 ft AGL at event
- 156 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KPWM 170451Z 36005KT 10SM FEW060 15/14 A3029 RMK AO2 SLP255 T01500139 402170122 $
Flight context
- RPA3627
- Republic Airways
- E75L
- KEWR → KPWM
- 2026-09-04 04:02 UTC
- KPWM runway 11
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