Long landing rollout — N721G
KILG · 192026-08-01 06:19 UTC· CHALLENGER HC LLC· CL60
N721G (Challenger HC) was inbound to KILG on 2026-08-01. SkyMeter detected a long landing rollout at New Castle Airport (KILG) on runway 19 at 06:19 UTC. Trace data at the event: 49 ft AGL, 11 kt GS, 0 fpm vertical. METAR at the time reported 2 kt wind, 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)- HAZARDS6/9841 2026-07-29 14:00Z – 2026-08-11 03:00Z SFC–11,500 ft
11NM S CIMARRON, NM, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/0409 2026-07-30 04:00Z – 2026-08-12 04:00Z SFC–15,000 ft
9NM SW PUEBLO, CO, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC
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 → - SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft
Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 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 19
- 49 ft AGL at event
- 11 kt ground speed
- 0 fpm vertical
- 2 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KILG 171051Z 19004KT 10SM CLR 21/19 A3026 RMK AO2 SLP245 T02060189 PNO $
Flight context
- N721G
- Challenger HC
- CL60
- 2026-08-01 06:19 UTC
- KILG runway 19
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