FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Critical Care Services Inc Dba Agustawestland Philadelphia Co AW119MKII accident

13 Feb 2021 · Alexandria, MN, United States

Agustawestland Philadelphia Co AW119MKII · Accident: collision with terrain/object (non-CFIT) en route

From an unrecorded airport to Gleenwood, MN

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
CEN21LA128
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
Event fatalities
Unknown
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
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

Agustawestland Philadelphia Co AW119MKII

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
N352LL
Onboard fatalities
Unknown
Route Possible conflict
From not recordedTo Gleenwood, MN
Aircraft age
About 7 years (built 2014)
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
En route · climb to cruise
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 with terrain/object (non-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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airline transport pilot of the commercial air medical flight reported that during a climbing left turn on departure, he heard a “thud.” He confirmed with the crew they had not dropped anything, and they affirmed they had not. The pilot believed the helicopter had hit something and elected to return to the departure airport. The pilot scanned the air to find what they could have impacted but did not see anything and then assumed a cowling had become unlatched due to the cold and vibration. He landed and left the helicopter running while the crew looked over the helicopter. At this time, the pilot was notified the trip was cancelled so he shut down, refueled, and moved the helicopter into the hangar. Once in the hangar, the pilot noticed the leading edge of the main rotor blade was a dented with a hole through the blade just aft of the dent. What caused the substantial damage to the main rotor blade was not determined. The pilot reported there were no preaccident mechanical malfunctions or failures with the helicopter that would have precluded normal operation.

Probable cause

The helicopter’s impact with an object on departure that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN21LA128
Event ID
20210215102633
Case number
CEN21LA128
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, coordinates. 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: 1dcfe3b47a9d129efad27275b02bbd2e939345216381b17a41817ea4b8060b3a; retrieved 2026-09-16T13:38:39.894Z.