Return to field — N103HJ

KBTR · 31

2026-07-22 19:17 UTC· KBTR KBTR· PILOTINSIDE.COM LLC· HDJT

N103HJ (Pilotinside.Com) had departed KBTR on 2026-07-22. SkyMeter detected a return to field at Baton Rouge Metropolitan Airport (KBTR) on runway 31 at 19:17 UTC. Peak cruise altitude FL385, turnaround area near Walton, US. Approach stability score: 43/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). 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)
  • SECURITY6/6747 2026-07-20 12:30Z – 2026-07-24 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, July 20, 2026 through Friday, July 24, 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 31
  • 38583 ft AGL at event
  • 438 kt ground speed
  • 0 fpm vertical
  • Approach stability 43/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KBTR 300653Z AUTO 26005KT 10SM CLR 27/25 A2992 RMK AO2 SLP131 T02720250 $

Flight context

  • N103HJ
  • Pilotinside.Com
  • HDJT
  • KBTR → KBTR
  • 2026-07-22 19:17 UTC
  • KBTR runway 31

All events on this flight

Return to field 19:17:06 UTC · KBTR runway 31 · 38,583 ft AGL · 438 kt GS
Unstable approach 23:01:44 UTC · KBTR runway 04L · 1,139 ft AGL · 195 kt GS
Unstable approach 23:01:44 UTC · KBTR runway 04L · 1,139 ft AGL · 195 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· KBTR