CEN17FA355 · Bell 206L 3
Bell 206L 3 · Accident: controlled flight into terrain/object (CFIT) en route
From Roswell Air Center Airport (KROW) to Albuquerque International Sunport (KABQ)
Event
- NTSB case
- CEN17FA355
- 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
- 1 · 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
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
- N213TV
- Operator
- WQRE News 13
- Onboard fatalities
- Unknown
- Route
- From Roswell Air Center Airport (KROW), Roswell, NMTo Albuquerque International Sunport (KABQ), Albuquerque, NM
- Aircraft age
- About 28 years (built 1989)
- 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
- En route
- 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Psychological
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 was conducting a return cross-country business flight in a helicopter. The reported winds at the time of the accident were light, and visibility was at least 10 miles.
GPS data showed that the helicopter departed about 1554 on a northwest heading toward the destination airport. The data revealed that, for the last 5 minutes of the flight, the helicopter's GPS altitude varied between 6,200 and 6,456 ft. The terrain in the area of the accident was between 6,000 and 6,400 ft, and the initial impact point was at 6,330 ft. The last recorded data at 1635 showed the helicopter about 1.5 nautical miles from the accident site at a GPS altitude of 6,456 ft.
A person located near the accident site reported that he saw smoke on nearby ranch property, drove in the direction of the smoke to investigate, and found the helicopter wreckage.
The helicopter impacted terrain in open ranch land. A postcrash fire consumed most of the wreckage. All of the airplane's major components were located at the wreckage site. Ground scars and signatures were consistent with a slight, nose-low impact with terrain, and the wreckage path was about 300 ft long on a 293° heading, which was indicative of controlled flight into terrain.. Although the airframe and engine examinations were limited by impact and fire damage, they did not reveal evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation.
The pilot's cell phone was recovered, and a review of the phone records revealed that, at 1612, he called a car rental agency. An agency employee stated that she remembered the call well. She added that she could not tell that he was in a helicopter, but that he seemed "busy or distracted" and that, as they were talking about a future rental and she was "midsentence," the line was disconnected. Based on the available information, the pilot was likely using his cell phone during the low-altitude flight and became distracted, which resulted in controlled flight into terrain.
Probable cause
The pilot's distraction by a cell phone during a low-altitude flight, which resulted in controlled flight into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17FA355
- Event ID
- 20170916X35842
- Case number
- CEN17FA355
- 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: 1ca3d5212987d03cb00fd1a5f6f7f2f3cd65f69cf75d0cb1f65b175ccb688b0f; retrieved 2026-09-15T06:17:06.626Z.