Long landing rollout — FFT2742
KTTN · 242026-07-16 12:33 UTC· KMCO → KTTN· UMB BANK NA TRUSTEE· A20N
FFT2742 (UMB Bank NA) was operating from KMCO to KTTN on 2026-07-16. SkyMeter detected a long landing rollout at Trenton Mercer Airport (KTTN) on runway 24 at 12:33 UTC. Trace data at the event: 180 ft AGL, 5 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)- SECURITY6/3961 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Chester, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3967 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PHILADELPHIA, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3970 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3971 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4005 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/6442 2026-06-10 04:01Z – 2026-07-20 03:59Z SFC–1,000 ft
Philadelphia, PA, Wednesday, June 10, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - SECURITY6/7169 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV
View FAA NOTAM → - SECURITY6/7564 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC
View FAA NOTAM → - SECURITY6/7138 2026-07-10 14:07Z – 2026-07-21 03:59Z SFC–400 ft
Philadelphia, PA
View FAA NOTAM → - HAZARDS6/4931 2026-07-11 15:58Z – 2026-07-23 01:00Z SFC–3,000 ft
2NM NE SHALLOTTE, NC, Saturday, July 11, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/5843 2026-07-14 23:37Z – 2026-07-22 23:45Z SFC–4,200 ft
18NM SW WAYNESBORO, VA, Tuesday, July 14, 2026 through Wednesday, July 22, 2026 UTC
View FAA NOTAM → - SECURITY6/5640 2026-07-15 12:30Z – 2026-07-18 06:00Z SFC–2,500 ft
MAYPORT, FL, Wednesday, July 15, 2026 through Saturday, July 18, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/5186 2026-07-16 06:20Z – 2026-07-16 11:12Z SFC–180 ft
Cape Canaveral, FL, Thursday, July 16, 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 24
- 180 ft AGL at event
- 5 kt ground speed
- 0 fpm vertical
- 2 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KTTN 120653Z AUTO 03008KT 10SM OVC007 13/12 A2976 RMK AO2 LTG DSNT SW SLP072 T01280117
Flight context
- FFT2742
- UMB Bank NA
- A20N
- KMCO → KTTN
- 2026-07-16 12:33 UTC
- KTTN runway 24
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