Long landing rollout — ATN3326
KLAL · 282026-04-01 14:12 UTC· KABE → KLAL· CARGO AIRCRAFT MANAGEMENT INC· B763
ATN3326 (Cargo Aircraft Management) was operating from KABE to KLAL on 2026-04-01. SkyMeter detected a long landing rollout at Lakeland Linder International Airport (KLAL) on runway 28 at 14:12 UTC. Trace data at the event: 157 ft AGL, 8 kt GS, 0 fpm vertical. Approach stability score: 83/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 6 kt wind, 11,265 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/4875 2026-03-30 13:00Z – 2026-04-04 06:00Z SFC–2,500 ft
20NM NW MEDFORD, OR, Friday, July 10, 2026 through Saturday, July 25, 2026 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 28
- 157 ft AGL at event
- 8 kt ground speed
- 0 fpm vertical
- Approach stability 83/100
- 6 kt wind
- 0 kt crosswind component
- 11,265 m visibility
- KLAL 221250Z 09003KT 7SM BKN005 25/24 A2994
Flight context
- ATN3326
- Cargo Aircraft Management
- B763
- KABE → KLAL
- 2026-04-01 14:12 UTC
- KLAL runway 28
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