Return to field — RPA4662

KLGA · 31

2026-04-01 13:56 UTC· KLGA KLGA· REPUBLIC AIRWAYS INC· E75L

RPA4662 (Republic Airways) had departed KLGA on 2026-04-01. SkyMeter detected a return to field at La Guardia Airport (KLGA) on runway 31 at 13:56 UTC. Peak cruise altitude FL364, turnaround area near Wrightsville Beach, US. METAR at the time reported 0 kt wind, 16,093 m visibility. 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 →
  • SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/4875 2026-03-30 13:00Z – 2026-04-04 06:00Z SFC–2,500 ft

    20NM NW MEDFORD, OR, Friday, July 10, 2026 through Saturday, July 25, 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 31
  • 36438 ft AGL at event
  • 485 kt ground speed
  • 0 fpm vertical
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KLGA 162351Z 16007KT 10SM BKN060 BKN180 BKN250 23/18 A3028 RMK AO2 SLP253 T02280183 10261 20228 51001

Flight context

  • RPA4662
  • Republic Airways
  • E75L
  • KLGA → KLGA
  • 2026-04-01 13:56 UTC
  • KLGA runway 31

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

SkyMeter · trace data observed via ADS-B· KLGA