Unstable approach — EJA879

EJA879 (Alan JAY Automotive Management) was operating from KBZN to KBOS on 2026-07-19. SkyMeter detected a low approach-stability score at General Edward Lawrence Logan International Airport (KBOS) on runway 32 at 18:35 UTC. Trace data at the event: 1124 ft AGL, 155 kt GS. Approach stability score: 60/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 11 kt wind, 3 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/3959 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

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

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

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

  View FAA NOTAM →
• SECURITY6/5882 2026-07-17 16:30Z – 2026-07-20 04:00Z SFC–400 ft

  MINNEAPOLIS, MN, Friday, July 17, 2026 through Sunday, July 19, 2026 Local

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/5171 2026-07-18 16:00Z – 2026-07-19 21:30Z SFC–16,000 ft

  Sioux Falls, SD, Saturday, July 18, 2026 through Sunday, July 19, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/5201 2026-07-19 17:00Z – 2026-07-20 04:30Z SFC–400 ft

  madison, WI, Sunday, July 19, 2026 through Monday, July 20, 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