Air Methods Eurocopter Deutschland Gmbh EC135T2 accident
Eurocopter Deutschland Gmbh EC135T2 and DJI Air 3 · Accident: midair collision on approach
Event
- NTSB case
- ERA25LA129
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · Eurocopter Deutschland Gmbh EC135T2
- Aircraft type
- Eurocopter EC135
- Category
- Helicopter
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N405TJ
- Operator
- Air Methods
- Onboard fatalities
- Unknown
- Route
- From Abington Memorial Hospital Heliport (PN03), Abington, PATo Thomas Jefferson University Hospital Heliport (9PA8), Philadelphia, PA
- Aircraft age
- About 20 years (built 2005)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 135: Air Taxi & Commuter
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · DJI Air 3
- Aircraft type
- DJI AIR-3
- Category
- Unknown
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- Unknown
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 107: Small UAS
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Not recorded
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Not recorded
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Unknown
Cause areas
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The purpose of the helicopter flight was a medical resupply for a local hospital. According to the pilot of the helicopter, while on final approach to the hospital’s helipad, he heard and felt something impact the upper portion of the helicopter. After the impact sound, the pilot reported seeing a small black object fall down the right side of the windscreen. The pilot continued the approach to the helipad and landed uneventfully. After landing, an inspection of the helicopter revealed one of the main rotor blades sustained substantial damage. The pilot reported that there were no signs of bird snarge or feathers to indicate the impact was with a bird. After the accident, small unmanned aircraft system (sUAS) operator, who had been operating a sUAS in the area of the accident flight, reported to a Federal Aviation (FAA) office that he had heard a helicopter and attempted to land his sUAS. After the helicopter flew by, he reported that his control station lost contact with the sUAS. An FAA inspector and the sUAS operator were unsuccessful in their subsequent search for the sUAS. Multiple follow up attempts to interview the sUAS operator and to retrieve the flight controller’s datalog were unsuccessful. Based on the available information, the object that impacted the helicopter was likely the operator’s sUAS.
Probable cause
The sUAS operator’s failure to see and avoid a helicopter, resulting in a midair collision between the helicopter and the sUAS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA129
- Event ID
- 20250226199768
- Case number
- ERA25LA129
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 0101ed6291c330caf1e759415c20e962290d6dda7040f4968ff593c53fb56600; retrieved 2026-09-13T18:49:04.721Z.