Return to field — N372GB

KBNA · 20C

2026-08-14 21:28 UTC· KBNA KBNA· PALANGA LOGISTICS LLC· H25B

N372GB (Palanga Logistics) had departed KBNA on 2026-08-14. SkyMeter detected a return to field at Nashville International Airport (KBNA) on runway 20C at 21:28 UTC. Peak altitude 17,046 ft, turnaround area near Wilson County, US. Approach stability score: 41/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, 14,484 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft

    Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 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 20C
  • 17046 ft AGL at event
  • 378 kt ground speed
  • 0 fpm vertical
  • Approach stability 41/100
  • 0 kt wind
  • 0 kt crosswind component
  • 14,484 m visibility
  • KBNA 161153Z 16007KT 9SM FEW250 25/21 A3032 RMK AO2 SLP258 7//// T02500206 10272 20239 53023

Flight context

  • N372GB
  • Palanga Logistics
  • H25B
  • KBNA → KBNA
  • 2026-08-14 21:28 UTC
  • KBNA runway 20C

All events on this flight

Return to field 21:28:41 UTC · KBNA runway 20C · 17,046 ft AGL · 378 kt GS
Unstable approach 22:03:13 UTC · KBNA runway 31 · 1,695 ft AGL · 142 kt GS
Unstable approach 22:03:13 UTC · KBNA runway 31 · 1,695 ft AGL · 142 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· KBNA