Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

February 17, 2025 · Dji Air 3

Philadelphia, PA

Overview

Report Status
Probable Cause
Event Type
Accident
Date
February 17, 2025
Injury Outcomes
No injuries (4 uninjured)
Location
Philadelphia, PA
Aircraft
Dji Air 3 (2005)
Operator
Air Methods
Injuries
None
Aircraft Damage
Unknown
NTSB Number
ERA25LA129

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, a 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.

NTSB Probable Cause

The sUAS operator’s failure to see and avoid a helicopter, resulting in a midair collision between the helicopter and the sUAS.

Full 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.

Flight

Event TypeAccident
Event Time15:03 EST
Nearest AirportThomas Jefferson University Ho (1nm SSE)
RunwayH1
Runway Length40 ft
Runway Width40 ft
Flight Plan FiledNone
Flight Plan ActivatedUnknown
Aircraft FireUnknown
Aircraft ExplosionUnknown

Aircraft

AircraftDji Air 3
Aircraft CategoryUnknown
DamageUnknown
OperatorAir Methods
Operating RulePart 107
Engines4
Engine TypeTurboshaft
Engine DetailsSafran · ARRIUS 2B2 · Turboshaft · 633 | Safran · ARRIUS 2B2 · Turboshaft · 633
Seats4

People & Injuries

Injury SummaryNo injuries (4 uninjured)
Fatal0
Serious0
Minor0
Uninjured4
Total4
Crew 1Age 37 · First Class · None
Crew 2None
Crew 3None

Conditions

ConditionsVMC
LightDaylight
Wind270° @ 18 kt, gusting 28 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point37 F / 7 F
Altimeter29.94 inHg
Observation Time14:54
Weather SourceWFAC

Appendix: Source Data