DLH405 was operating from KJFK to EDDF on 2026-07-15. SkyMeter detected a go-around at Frankfurt am Main Airport (EDDF) on runway 07L at 09:28 UTC. Trace data at the event: 672 ft AGL, 136 kt GS. METAR at the time reported 10 kt wind, 3 kt crosswind component, 9,994 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/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/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/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/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/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/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 → - SECURITY6/7080 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft
Providence, RI
View FAA NOTAM → - SECURITY6/7081 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft
Smithfield, RI
View FAA NOTAM → - SECURITY6/3451 2026-07-11 11:00Z – 2026-07-17 03:00Z SFC–2,000 ft
Boston, MA, Saturday, July 11, 2026 through Thursday, July 16, 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 07L
- 672 ft AGL at event
- 136 kt ground speed
- 0 fpm vertical
- 10 kt wind
- 3 kt crosswind component
- 9,994 m visibility
- EDDF 161050Z AUTO 31009KT 280V340 CAVOK 22/10 Q1015 NOSIG
Flight context
- DLH405
- A333
- KJFK → EDDF
- 2026-07-15 09:28 UTC
- EDDF runway 07L
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