Return to field — TIGER7
KMHV · 262026-08-13 14:59 UTC· KMHV → KMHV· NATIONAL TEST PILOT SCHOOL· SBR1
TIGER7 (National Test Pilot School) had departed KMHV on 2026-08-13. SkyMeter detected a return to field at Mojave Airport (KMHV) on runway 26 at 14:59 UTC. Peak cruise altitude FL384, turnaround area near Kernville, US. Approach stability score: 57/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/2274 2026-08-05 19:25Z – 2026-08-15 04:00Z SFC–13,500 ft
25NM S BISHOP, CA, Wednesday, August 5, 2026 through Saturday, August 15, 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 26
- 38496 ft AGL at event
- 430 kt ground speed
- 0 fpm vertical
- Approach stability 57/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- METAR KMHV 160335Z AUTO 25010KT 10SM CLR 23/05 A2992 RMK AO2 T02280051 $
Flight context
- TIGER7
- National Test Pilot School
- SBR1
- KMHV → KMHV
- 2026-08-13 14:59 UTC
- KMHV runway 26
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