Unstable approach — EJA832

EJA832 (Patterson Anna) was operating from KLVK to K0V4 on 2026-09-04. SkyMeter detected a low approach-stability score at Brookneal/Campbell County Airport (K0V4) on runway 06 at 17:59 UTC. Trace data at the event: 1705 ft AGL, 129 kt GS. Approach stability score: 30/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 6 kt wind, 6 kt crosswind component, 16,093 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.

• SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

  BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

  SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

  View FAA NOTAM →
• HAZARDS6/7113 2026-08-22 20:30Z – 2026-09-05 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Saturday, August 22, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7127 2026-08-23 05:30Z – 2026-09-06 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7283 2026-08-23 16:00Z – 2026-09-06 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7347 2026-08-24 13:00Z – 2026-09-07 04:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7530 2026-08-24 17:00Z – 2026-09-06 03:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7463 2026-08-25 12:00Z – 2026-09-08 08:00Z SFC–16,500 ft

  1NM NE OURAY, CO, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7654 2026-08-25 13:00Z – 2026-09-07 04:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Tuesday, August 25, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7986 2026-08-25 21:45Z – 2026-09-07 04:00Z SFC–12,000 ft

  32NM SW TOOELE, UT, Tuesday, August 25, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8332 2026-08-26 17:45Z – 2026-09-05 04:00Z SFC–11,000 ft

  51NM NE FALLON, NV, Wednesday, August 26, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8507 2026-08-27 03:15Z – 2026-09-05 03:00Z SFC–11,000 ft

  51NM NE FALLON, NV, Thursday, August 27, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0223 2026-09-02 02:30Z – 2026-09-16 03:00Z SFC–8,000 ft

  30NM NE MERCED, CA, Wednesday, September 2, 2026 through Wednesday, September 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0800 2026-09-03 14:50Z – 2026-09-06 02:30Z SFC–14,000 ft

  BAILEY, CO, Thursday, September 3, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0953 2026-09-04 12:00Z – 2026-09-18 08:00Z SFC–13,000 ft

  1NM NE OURAY, CO, Friday, September 4, 2026 through Friday, September 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1127 2026-09-04 15:25Z – 2026-09-11 04:00Z SFC–12,000 ft

  10NM SW TELLURIDE, CO, Friday, September 4, 2026 through Friday, September 11, 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.

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