Long landing rollout — UPS1345
KFTK · 272026-08-27 04:15 UTC· KFLL → KFTK· UNITED PARCEL SERVICE CO· B763
UPS1345 (United Parcel Service) was operating from KFLL to KFTK on 2026-08-27. SkyMeter detected a long landing rollout at Godman Army Air Field (KFTK) on runway 27 at 04:15 UTC. Trace data at the event: 482 ft AGL, 19 kt GS, 0 fpm vertical. METAR at the time reported 4 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.
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 → - SECURITY6/7271 2026-08-24 12:30Z – 2026-08-29 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, August 24, 2026 through Saturday, August 29, 2026 Local
View FAA NOTAM → - SECURITY6/7590 2026-08-26 05:00Z – 2026-08-27 09:30Z SFC–17,999 ft
Macon, GA, Wednesday, August 26, 2026 through Thursday, August 27, 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 27
- 482 ft AGL at event
- 19 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KFTK 161855Z AUTO 00000KT 10SM CLR 33/23 A3025 RMK AO2 SLP236 T03320226
Flight context
- UPS1345
- United Parcel Service
- B763
- KFLL → KFTK
- 2026-08-27 04:15 UTC
- KFTK runway 27
All events on this flight
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