Long landing rollout — N763DB
KPIE · 35R2026-01-13 17:31 UTC· KPBI → KPIE· TRANS EXEC AIR SERVICE INC· GLF4
N763DB (Trans Exec AIR Service) was operating from KPBI to KPIE on 2026-01-13. SkyMeter detected a long landing rollout at St Petersburg Clearwater International Airport (KPIE) on runway 35R at 17:31 UTC. Trace data at the event: 19 ft AGL, 1 kt GS, 0 fpm vertical. Approach stability score: 84/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, 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 →
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 35R
- 19 ft AGL at event
- 1 kt ground speed
- 0 fpm vertical
- Approach stability 84/100
- 6 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- METAR KPIE 270253Z 34004KT 10SM CLR 23/16 A2994 RMK AO2 SLP139 T02330161 51011
Flight context
- N763DB
- Trans Exec AIR Service
- GLF4
- KPBI → KPIE
- 2026-01-13 17:31 UTC
- KPIE runway 35R
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