Paradigm Helicopters Sikorsky Aircraft Corp S-76 D accident
Sikorsky Aircraft Corp S-76 D · Accident: collision during takeoff/landing
From Dallas Love Field (DAL) to Mirasol Hills Heliport (TA22)
Event
- NTSB case
- CEN25LA356
- 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
Sikorsky Aircraft Corp S-76 D
- Aircraft type
- Sikorsky S-76
- 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
- N36RP
- Operator
- Paradigm Helicopters
- Onboard fatalities
- Unknown
- Route
- From Dallas Love Field (DAL), Dallas, TXTo Mirasol Hills Heliport (TA22), Dripping Springs, TX
- Aircraft age
- About 12 years (built 2013)
- 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
- Landing
- 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
- Collision during takeoff/landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The purpose of the on-demand night flight in the helicopter was to transport the passenger from a commercial airport to a private heliport on a ranch in a rural area. Due to previous issues with the helicopter’s autopilot system and the possible concern of losing control in instrument meteorological conditions, the captain decided not to perform an instrument flight rules flight to the heliport. During the flight, an instrument approach was loaded into the helicopter’s flight management system, but it was not activated. Additionally, each pilot had an Apple iPad mounted in the cockpit, that was utilizing ForeFlight with the heliport coordinates loaded into ForeFlight. During the approach to the heliport, the captain contacted the ranch manager via text message on a cellular phone, to ensure the heliport floodlight system was activated. The first officer activated the heliport ground lights, which were a green color, via a radio frequency. Both pilots acknowledged observing green lights in their sight. The captain reported that he “cross-checked” the map display with the outside visual references to confirm alignment with the heliport, which he thought had matched. The first officer extended the landing gear, he completed the before landing checklist, and he then transitioned to viewing outside of the helicopter to try and visually acquire the heliport. The captain delayed turning on the landing lights until closer to the heliport to avoid glare from moisture and haze reflecting in the light beams. The captain began maneuvering the helicopter for landing. Within seconds, the captain lost outside visual references, and he transitioned to instruments. The first officer looked inside the cockpit and observed the radar altimeter indicated 20 ft. Before the first officer could verbally call out to execute a go around, the helicopter terrain awareness and warning system activated an alert, and the helicopter impacted trees and terrain. The helicopter sustained substantial damage to the fuselage, the main rotor system, the tail boom, the empennage, and the tail rotor system. The captain reported there were no preimpact mechanical malfunctions or failures with the airframe or the two turboshaft engines that would have precluded normal operation. A review of meteorological data at the time of the accident showed dark night conditions were present for the accident site. It is likely the flight crew failed to properly identify the heliport in dark night conditions, which resulted in the flight crew attempting to land at the incorrect location. It is also likely the flight crew failed to properly utilize navigation information and visual cues to verify the location of the heliport.
Probable cause
The flight crew’s failure to properly identify the heliport in dark night conditions, which resulted in the flight crew attempting to land and a subsequent impact with trees and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA356
- Event ID
- 20250902200918
- Case number
- CEN25LA356
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2025-09-01.
- API snapshot SHA-256: 342c2d66cf9eaa5aee42400293c3003248d788262773bea42c7ea6bb3e4b6930; retrieved 2026-09-16T20:17:44.719Z.