Long landing rollout — NEW111

KILG · 19

2026-05-19 10:10 UTC· KTEB → KILG· METROPOLITAN TELECOMMUNICATIONS CORP OF DE LLC· CL60

▶ Replay 📊 Analyse

NEW111 (Metropolitan Telecommunications Corp of DE) was operating from KTEB to KILG on 2026-05-19. SkyMeter detected a long landing rollout at New Castle Airport (KILG) on runway 19 at 10:10 UTC. Trace data at the event: 72 ft AGL, 14 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 4 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/0907 2026-05-18 13:00Z – 2026-05-19 20:00Z SFC–1,000 ft

    Morristown, NJ, Monday, May 18, 2026 through Tuesday, May 19, 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 19
  • 72 ft AGL at event
  • 14 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KILG 201251Z 17013G19KT 10SM SCT025 BKN034 OVC048 22/19 A3001 RMK AO2 SLP160 T02170189 PNO $

Flight context

  • NEW111
  • Metropolitan Telecommunications Corp of DE
  • CL60
  • KTEB → KILG
  • 2026-05-19 10:10 UTC
  • KILG runway 19

All events on this flight

Long landing rollout 10:10:44 UTC · KILG runway 19 · 72 ft AGL · 14 kt GS
Long landing rollout 10:10:44 UTC · KILG runway 19 · 72 ft AGL · 14 kt GS

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· KILG