ITY680 was operating from LIRF to SAEZ on 2025-09-18. SkyMeter detected a emergencydescent at 09:51 UTC. Trace data at the event: 25586 ft AGL, 390 kt GS. METAR at the time reported 10 kt wind, 7 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/8818 2016-03-23 15:38Z – 2027-10-18 11:03Z
Special Notice, USA
View FAA NOTAM → - SECURITY0/0367 2020-01-15 00:01Z – 2027-10-18 11:03Z
USA, Wednesday, January 15, 2020 UTC
View FAA NOTAM → - SPECIAL1/5060 2021-09-29 16:37Z – 2027-10-18 11:03Z SFC–999 ft
USA, Wednesday, September 29, 2021 UTC
View FAA NOTAM → - SECURITY2/8783 2022-02-28 19:15Z – 2027-10-18 11:03Z
USA, Monday, February 28, 2022 UTC
View FAA NOTAM → - SECURITY4/1789 2024-06-21 17:35Z – 2027-10-18 11:03Z
USA, Friday, June 21, 2024 UTC
View FAA NOTAM → - SECURITY4/2565 2024-06-24 16:00Z – 2027-10-18 11:03Z
USA, Monday, June 24, 2024 UTC
View FAA NOTAM → - SECURITY4/9433 2024-09-03 20:30Z – 2027-10-18 11:03Z
USA, Tuesday, September 3, 2024 UTC
View FAA NOTAM → - SECURITY5/6874 2025-03-01 05:00Z – 2027-03-31 05:00Z
USA, Saturday, March 1, 2025 through Wednesday, March 31, 2027 UTC
View FAA NOTAM → - SECURITY5/7224 2025-09-03 15:10Z – 2027-10-18 11:03Z
WASHINGTON, DC, Wednesday, September 3, 2025 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
- 25586 ft AGL at event
- 390 kt ground speed
- 0 fpm vertical
- 10 kt wind
- 7 kt crosswind component
Flight context
- ITY680
- A359
- LIRF → SAEZ
- 2025-09-18 09:51 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