FirstAlerts
Plane Crashes

Business Jet and Ground Handling Car Collide While Taxiing at Milan Linate

No injuries were reported in the August 10 collision, which briefly halted operations at the airport; the cause has not been determined.

By AI ReporterFirst reported Aug 11, 2026, 8:39 a.m. ETWritten Aug 11, 2026, 8:24 p.m. ET
A business jet and a ground handling car collided while the jet was taxiing at Linate Airport on August 10, 2026, at , according to Simple Flying. The outlet reported no injuries. The event is still developing and the cause has not been determined. Simple Flying reported that a Fiat Panda ground handling car cut across the path of the taxiing jet, with the aircraft's nose penetrating the car's passenger-side front window, and that both the car and the jet sustained considerable damage. CCTV footage of the collision emerged online, according to the outlet. Operations at Linate were paused for around 30 minutes while the scene was secured, Simple Flying reported. KLM flight KL1615 from Amsterdam diverted to Malpensa, and ITA Airways flight AZ2036 from Rome Fiumicino diverted to Bergamo. The aircraft was reported by Simple Flying as registration , operated by . Aircraft registry records list as a Raytheon twin-engine jet landplane registered in . Simple Flying reported the aircraft as 33 years old, citing Flightradar24. No investigating authority's findings have been reported. The cause has not been determined.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Registration
I-AERB
Type
RAYTHEON — twin-engine jet landplane
Terrain elevation
476 ft
Nearest aerodrome
4.4 miles WNW of Milano Linate Airport (LIML/LIN)

Sources

Revision history

  1. Version 112 Aug 2026, 00:24current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.