SLI2609 had departed KDTW on 2026-08-18. SkyMeter recorded a 7700 transponder transmission at 15:29 UTC. Code 7700 indicates a general emergency declaration (e.g. engine, medical, smoke). A sustained transmission is normally accompanied by ATC priority handling. Trace data at the event: 40432 ft AGL, 484 kt GS. METAR at the time reported 9 kt wind, 1 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft
South Padre Island, TX, Tuesday, May 6, 2025 Local
View FAA NOTAM → - SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft
Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC
View FAA NOTAM → - HAZARDS6/2568 2026-08-06 14:22Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2575 2026-08-06 15:06Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2751 2026-08-07 00:16Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Friday, August 7, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3249 2026-08-10 15:17Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Monday, August 10, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3405 2026-08-10 16:03Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Monday, August 10, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/2574 2026-08-13 12:00Z – 2026-08-24 05:00Z SFC–400 ft
des moines, IA, Thursday, August 13, 2026 through Monday, August 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4962 2026-08-13 18:15Z – 2026-08-20 18:00Z SFC–2,000 ft
YOUNGSPORT, TX, Thursday, August 13, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft
Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - SECURITY6/3628 2026-08-17 12:00Z – 2026-08-23 23:59Z SFC–400 ft
SAINT LOUIS, MO, Monday, August 17, 2026 through Sunday, August 23, 2026 Local
View FAA NOTAM → - SECURITY6/5153 2026-08-18 05:00Z – 2026-08-20 09:30Z SFC–17,999 ft
Macon, GA, Tuesday, August 18, 2026 through Thursday, August 20, 2026 Local
View FAA NOTAM → - HAZARDS6/5090 2026-08-18 13:00Z – 2026-08-18 20:00Z SFC–2,000 ft
HALLSVILLE, MO, Tuesday, August 18, 2026 UTC
View FAA NOTAM → - HAZARDS6/5092 2026-08-18 13:00Z – 2026-08-18 20:00Z SFC–2,000 ft
HARRISBURG, MO, Tuesday, August 18, 2026 UTC
View FAA NOTAM → - SECURITY6/5653 2026-08-18 13:30Z – 2026-08-18 16:30Z SFC–999 ft
Destin, FL, Tuesday, August 18, 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
- 40432 ft AGL at event
- 484 kt ground speed
- 0 fpm vertical
- 9 kt wind
- 1 kt crosswind component
Flight context
- SLI2609
- E190
- 2026-08-18 15:29 UTC
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