Unstable approach — TRACR02

KNGU · 28

2026-07-05 01:04 UTC· KNGU KNGU· E2

TRACR02 was operating from KNGU to KNGU on 2026-07-05. SkyMeter detected a low approach-stability score at Norfolk Naval Station (Chambers Field) (KNGU) on runway 28 at 01:04 UTC. Trace data at the event: 1045 ft AGL, 150 kt GS. METAR at the time reported 8 kt wind, 8 kt crosswind component, 14,484 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • AIR SHOWS/SPORTS6/0944 2026-07-03 14:00Z – 2026-07-05 03:30Z SFC–15,000 ft

    Washington, DC, Friday, July 3, 2026 through Sunday, July 5, 2026 UTC

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/1371 2026-07-03 14:00Z – 2026-07-05 03:30Z SFC–15,000 ft

    Washington, DC, Friday, July 3, 2026 through Sunday, July 5, 2026 UTC

    View FAA NOTAM →
  • VIP6/2673 2026-07-04 12:00Z – 2026-07-04 22:30Z SFC–9,999 ft

    Sterling, VA, Saturday, July 4, 2026 Local

    View FAA NOTAM →
  • SECURITY6/2636 2026-07-04 14:00Z – 2026-07-05 03:00Z SFC–400 ft

    Williamsburg, VA, Saturday, July 4, 2026 through Saturday, July 4, 2026 Local

    View FAA NOTAM →
  • VIP6/1088 2026-07-04 20:30Z – 2026-07-05 03:59Z SFC–17,999 ft

    Washington, DC, Saturday, July 4, 2026 through Saturday, July 4, 2026 Local

    View FAA NOTAM →
  • VIP6/1090 2026-07-04 20:30Z – 2026-07-05 03:59Z SFC–17,999 ft

    Washington, DC, Saturday, July 4, 2026 through Saturday, July 4, 2026 Local

    View FAA NOTAM →
  • VIP6/1095 2026-07-04 20:30Z – 2026-07-05 03:59Z SFC–17,999 ft

    Washington, DC, Saturday, July 4, 2026 through Saturday, July 4, 2026 Local

    View FAA NOTAM →
  • VIP6/1372 2026-07-04 20:30Z – 2026-07-05 03:59Z SFC–17,999 ft

    Washington, DC, Saturday, July 4, 2026 through Saturday, July 4, 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 28
  • 1045 ft AGL at event
  • 150 kt ground speed
  • 0 fpm vertical
  • 8 kt wind
  • 8 kt crosswind component
  • 14,484 m visibility
  • KNGU 150959Z 02005KT 9SM FEW015 SCT045 BKN250 26/24 A3007 RMK AO2 SLP181 T02560239 $

Flight context

  • TRACR02
  • E2
  • KNGU → KNGU
  • 2026-07-05 01:04 UTC
  • KNGU runway 28

All events on this flight

Unstable approach 01:04:54 UTC · KNGU runway 28 · 1,045 ft AGL · 150 kt GS
Unstable approach 01:04:54 UTC · KNGU runway 28 · 1,045 ft AGL · 150 kt GS
Unstable approach 01:04:54 UTC · KNGU runway 28 · 1,045 ft AGL · 150 kt GS
Unstable approach 01:04:54 UTC · KNGU runway 28 · 1,045 ft AGL · 150 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· KNGU