FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09LA464 · Eurocopter Deutschland Gmbh EC-145

17 Aug 2009 · North Captiva Island, FL, United States

Lee County Division of Public Safety Eurocopter Deutschland Gmbh EC-145 · Accident: controlled flight into terrain/object (CFIT) on approach

From Page Field (FMY) to Salty Approach Airport (FL90)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA09LA464
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
Unknown
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
General aviation
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

Eurocopter Deutschland Gmbh EC-145

Aircraft type
Eurocopter EC-145
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
N911LZ
Onboard fatalities
Unknown
Route Narrative disagrees
From Page Field (FMY), Fort Myers, FLTo Salty Approach Airport (FL90), N Captiva Isl., FL
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 91: General Aviation
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
Controlled flight into terrain/object (CFIT)
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The emergency medical services (EMS) helicopter was on a night, over-water flight in visual meteorological conditions when the accident occurred. The pilot and two medical crewmembers were en route to pick up a patient on a barrier island. The pilot flew over the water with the autopilot engaged (altitude acquisition mode), at an altitude of 1,000 feet. While en route, the pilot unsuccessfully attempted to contact the fire department on the island to obtain landing zone information. When the helicopter was approximately 3 minutes from landing, the pilot selected 500 feet using the autopilot and the helicopter initiated a descent to that altitude. Unable to contact the fire department, the pilot likely became preoccupied with the task as well as the visual acquisition of the landing. The descent-power setting, which was manually controlled by the pilot, was not adequate to capture the selected altitude, and maintain 60 knots. As designed, the helicopter likely continued its descent with the autopilot engaged until it impacted the water. The pilot observed an amber indication on the primary flight display just before impact, which indicated the autopilot was engaged, and confirmed this most likely scenario.

A post-accident examination of the helicopter revealed no pre-impact mechanical anomalies. After the impact, the dispatcher initiated a re-boot of her computer, rather than a search for the helicopter, when the helicopter's movement stopped on her screen. However, the fire department on scene initiated a search, and the crewmembers were rescued within a short timeframe. Had the crewmembers sustained serious injuries during the accident, the dispatcher's failure to initiate a search may have reduced the survivability of the accident.

Probable cause

The pilot's failure to arrest the helicopter's descent, which resulted in controlled flight into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09LA464
Event ID
20090817X80103
Case number
ERA09LA464
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. 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: c88f6b0131198ed5686ff5506ed482fb4aa8ac2977c2b14c219b78cf9729ced7; retrieved 2026-09-15T12:48:40.593Z.