Long landing rollout — N515GT

N515GT (Embraer Executive Aircraft) was inbound to K4T2 on 2026-02-18. SkyMeter detected a long landing rollout at Kenneth Copeland Airport (K4T2) on runway 35 at 18:35 UTC. Trace data at the event: 629 ft AGL, 5 kt GS. 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 5 kt wind, 4 kt crosswind component. 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.

• SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft

  South Padre Island, TX, Tuesday, May 6, 2025 Local

  View FAA NOTAM →
• 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 →
• SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

  OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

  View FAA NOTAM →
• SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft

  Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

  View FAA NOTAM →
• SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft

  Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 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.

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