Unstable approach — EJA873

EJA873 (Adventures & Ingredients) was inbound to KTEB on 2026-07-03. SkyMeter detected a low approach-stability score at Teterboro Airport (KTEB) on runway 24 at 19:35 UTC. Trace data at the event: 1110 ft AGL, 133 kt GS. Approach stability score: 58/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 9 kt wind, 9 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/3955 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Smithfield, RI, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3963 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  FOXBOROUGH, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3949 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Providence, RI, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

  View FAA NOTAM →
• SECURITY6/1081 2026-07-01 12:00Z – 2026-07-09 16:00Z SFC–2,000 ft

  New York, NY, Wednesday, July 1, 2026 through Thursday, July 9, 2026 Local

  View FAA NOTAM →
• SECURITY6/1240 2026-07-01 12:00Z – 2026-07-09 16:00Z SFC–2,000 ft

  New York, NY, Wednesday, July 1, 2026 through Thursday, July 9, 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.

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