EIN123 was operating from EIDW to KORD on 2026-08-09. SkyMeter detected a go-around at Chicago O'Hare International Airport (KORD) on runway 10L at 19:40 UTC. Trace data at the event: 850 ft AGL, 154 kt GS. METAR at the time reported 7 kt wind, 4 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/2790 2026-07-02 22:30Z – 2026-09-15 03:59Z SFC–400 ft
St. George, ME, Thursday, July 2, 2026 through Monday, September 14, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/0460 2026-08-06 13:00Z – 2026-08-17 05:00Z SFC–400 ft
Milwaukee, WI, Thursday, August 6, 2026 through Monday, August 17, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/0676 2026-08-07 14:00Z – 2026-08-09 22:00Z SFC–16,000 ft
Rochester, NY, Friday, August 7, 2026 through Sunday, August 9, 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 10L
- 850 ft AGL at event
- 154 kt ground speed
- 0 fpm vertical
- 7 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KORD 150051Z 05008KT 10SM FEW014 SCT070 OVC140 23/21 A3011 RMK AO2 SLP191 T02330206
Flight context
- EIN123
- A333
- EIDW → KORD
- 2026-08-09 19:40 UTC
- KORD runway 10L
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