Long landing rollout — N3054W
KLHM · 332026-07-15 17:00 UTC· 25CL → KO52· MOES CROP DUSTING SERVICE INC· AT8T
N3054W (Moes Crop Dusting Service) was operating from 25CL to KO52 on 2026-07-15. SkyMeter detected a long landing rollout at Lincoln Regional Karl Harder Field (KLHM) on runway 33 at 17:00 UTC. Trace data at the event: 22 ft AGL, 20 kt GS, 0 fpm vertical. Approach stability score: 41/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 2 kt wind, 2 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/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft
BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 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 33
- 22 ft AGL at event
- 20 kt ground speed
- 0 fpm vertical
- Approach stability 41/100
- 2 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- METAR KLHM 162315Z AUTO 17008KT 150V210 10SM CLR 26/09 A2987 RMK AO1
Flight context
- N3054W
- Moes Crop Dusting Service
- AT8T
- 25CL → KO52
- 2026-07-15 17:00 UTC
- KLHM runway 33
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