Return to field — N924NA

KEFD · 35R

2026-08-27 12:09 UTC· KEFD → KEFD· NATIONAL AERONAUTICS AND SPACE ADMINISTRATION· T38

▶ Replay 📊 Analyse

N924NA (National Aeronautics and Space Administration) had departed KEFD on 2026-08-27. SkyMeter detected a return to field at Ellington Airport (KEFD) on runway 35R at 12:09 UTC. Peak cruise altitude FL425, turnaround area near Luling, US. Approach stability score: 91/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 0 kt wind, 11,265 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/8400 2026-08-26 18:03Z – 2026-08-27 17:58Z SFC–2,000 ft

    PASADENA, TX, Wednesday, August 26, 2026 through Thursday, August 27, 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 35R
  • 42533 ft AGL at event
  • 517 kt ground speed
  • 0 fpm vertical
  • Approach stability 91/100
  • 0 kt wind
  • 0 kt crosswind component
  • 11,265 m visibility
  • KEFD 171854Z 04007KT 7SM VCTS BKN012 27/25 A3014 RMK LTG DSNT E W

Flight context

  • N924NA
  • National Aeronautics and Space Administration
  • T38
  • KEFD → KEFD
  • 2026-08-27 12:09 UTC
  • KEFD runway 35R

All events on this flight

Return to field 12:09:27 UTC · KEFD runway 35R · 42,533 ft AGL · 517 kt GS
EmergencyDescent 13:21:46 UTC · · 30,481 ft AGL · 404 kt GS
EmergencyDescent 13:21:46 UTC · · 30,481 ft AGL · 404 kt GS

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

SkyMeter · trace data observed via ADS-B· KEFD