CEN13TA535 · Bell 206L-3
State of Illinois Bell 206L-3 · Accident: abrupt maneuver while maneuvering
From Dalhart Municipal Airport (DHT) to Albuquerque International Sunport (ABQ)
Event
- NTSB case
- CEN13TA535
- 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
- Government
- 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
Bell 206L-3
- Aircraft type
- Bell 206
- 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
- N721LL
- Operator
- State of Illinois
- Onboard fatalities
- Unknown
- Route
- From Dalhart Municipal Airport (DHT), Dalhart, TXTo Albuquerque International Sunport (ABQ), Albuquerque, NM
- 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
- Public Aircraft
- 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
- Maneuvering
- 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
- Abrupt maneuver
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the helicopter was established in cruise flight on a west-southwest course at 300 feet above ground level before the accident. The pilot stated that about 25 minutes into the flight, he observed "multiple large black birds" in the helicopter's flightpath and initiated an "immediate hard turn to the right to avoid" them. He subsequently noted an increase in main rotor speed and adjusted accordingly. The pilot rolled out on a reciprocal heading, leveled the helicopter, and began to slow down. He noticed that the descent rate was not decreasing. The helicopter touched down "hard," seemed to bounce and came to rest about 100 yards from the initial touchdown point. The pilot reported no preaccident failures or malfunctions with the helicopter that would have precluded normal operation.
Probable cause
The pilot's failure to arrest the descent following an abrupt maneuver to avoid birds, which resulted in an impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13TA535
- Event ID
- 20130909X10032
- Case number
- CEN13TA535
- 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: 0ed4ca7f1d420e7789d3572e1bfa614ab59f7d96b9db8436dda60e0d984d218c; retrieved 2026-09-15T22:47:35.208Z.