CEN24FA083 · Just HIGHLANDER
Just HIGHLANDER · Accident: collision during takeoff/landing
From Dolores, CO to Cortez Municipal Airport (CEZ)
Event
- NTSB case
- CEN24FA083
- 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
- 2 · 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
- 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
Just HIGHLANDER
- Aircraft type
- Just HIGHLANDER
- Category
- Airplane
- 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
- N712DG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dolores, COTo Cortez Municipal Airport (CEZ), Cortez, CO
- Aircraft age
- About 13 years (built 2011)
- 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
- Takeoff
- 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane departed the private, 1,800-ft dirt airstrip for a short flight to another airport. When the airplane did not arrive, an Alert Notice (ALNOT) was issued and a search began. One day later, the airplane wreckage was located beyond the departure end of the private dirt runway. The airplane was destroyed by a postimpact fire. There were no witnesses to the accident and no flight track data associated with the accident flight. A local pilot flying in the area reported that he saw 3 tire tracks on the snow-covered dirt runway near the estimated time that the accident occurred; however, investigators were unable to determine the flight track of the airplane, the time of departure, or the time of the accident. The airplane came to rest on snow-covered ground about 650 ft beyond the departure end of the runway. A barbed wire fence was between the runway and the wreckage and exhibited damage consistent with impact with the airplane. Barbed wire was wrapped around the root of one of the propeller blades about 3 times. Snow in the time between the departure and when the airplane was located masked any ground scars that may have been made during the impact sequence. The postimpact fire destroyed the instrument panel and precluded functional testing of any flight instruments. Flight control continuity from the cockpit to the ailerons, elevator, and rudder was confirmed. The engine separated from the fuselage and sustained fire damage. Both main landing gear struts were bent up and both wings were impact-separated. The engine was fire-damaged and could not be functionally tested. Examination of the airframe and engine revealed no pre-impact mechanical anomalies that would have precluded normal operation. Damage to the airplane was consistent with a loss of control and subsequent collision with the barbed fence and terrain. Investigators were unable to determine the reason for the loss of control.
Probable cause
The pilot’s collision with a fence while taking off from a snow-covered dirt airstrip.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24FA083
- Event ID
- 20240107193620
- Case number
- CEN24FA083
- 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, cause areas. 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: b93649156744a6fa91740e143c697ee033b024b315c61c2724747e950e1c8eb5; retrieved 2026-09-15T08:09:53.379Z.