Long landing rollout — N700NA
GA14 · 272026-06-22 12:51 UTC· KRYY → GA14· ATLANTA AIR CHARTER INC· BE20
N700NA (Atlanta AIR Charter) was operating from KRYY to GA14 on 2026-06-22. SkyMeter detected a long landing rollout at Pinebloom Plantation Airport (GA14) on runway 27 at 12:51 UTC. Trace data at the event: 219 ft AGL, 18 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 5 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3991 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3998 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Atlanta, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/8212 2026-06-17 04:01Z – 2026-07-17 03:59Z SFC–400 ft
Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 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
- 219 ft AGL at event
- 18 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 5 kt crosswind component
Flight context
- N700NA
- Atlanta AIR Charter
- BE20
- KRYY → GA14
- 2026-06-22 12:51 UTC
- GA14 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