Long landing rollout — RPA4779

RPA4779 (Republic Airways) was operating from KLGA to KSAV on 2026-08-01. SkyMeter detected a long landing rollout at Savannah Hilton Head International Airport (KSAV) on runway 19 at 00:19 UTC. Trace data at the event: 42 ft AGL, 1 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 3 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.

• 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 →
• HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft

  2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• SECURITY6/0567 2026-07-31 18:00Z – 2026-08-02 23:30Z SFC–2,000 ft

  Morristown, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• VIP6/0568 2026-07-31 19:00Z – 2026-08-03 22:30Z SFC–4,999 ft

  Middleburg, VA, Friday, July 31, 2026 through Monday, August 3, 2026 Local

  View FAA NOTAM →
• VIP6/9922 2026-07-31 19:15Z – 2026-08-02 22:45Z SFC–17,999 ft

  Bedminster, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• VIP6/9923 2026-07-31 19:15Z – 2026-08-02 22:45Z SFC–17,999 ft

  Bedminster, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• VIP6/0695 2026-07-31 20:45Z – 2026-07-31 22:30Z SFC–17,999 ft

  Morristown, NJ, Friday, July 31, 2026 Local

  View FAA NOTAM →
• VIP6/0696 2026-07-31 20:45Z – 2026-07-31 22:30Z SFC–17,999 ft

  Morristown, NJ, Friday, July 31, 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.

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