CEN18FA227 · Cessna 172N N
Aero Photo Cessna 172N N · Accident: controlled flight into terrain/object (CFIT) while maneuvering
From Midland Airpark (MDD) to Austin Air Ranch Airport (88R)
Event
- NTSB case
- CEN18FA227
- 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
- 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
Cessna 172N N
- Aircraft type
- Cessna 172
- 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
- N734BS
- Operator
- Aero Photo
- Onboard fatalities
- Unknown
- Route
- From Midland Airpark (MDD), Midland, TXTo Austin Air Ranch Airport (88R), Spicewood, TX
- Aircraft age
- About 41 years (built 1977)
- 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
- 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
- Controlled flight into terrain/object (CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire
- 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
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane had completed an aerial photography mission with a pilot and passenger aboard and was en route to the destination airport. Video and photographic evidence obtained from two devices located in the wreckage (a Garmin Aera 560 portable GPS device and a GoPro Hero 4 action camera) and an online social media post indicated that the pilot was operating the airplane at high speeds and low altitudes during the accident flight. Photographs taken from within the airplane showed the canyon, wooden poles, and suspended power lines that the airplane eventually struck. In the final image retrieved from the GoPro camera, the airplane was in a moderate left bank at a similar altitude as the surrounding canyon and power lines and was heading toward the power lines. Given the image timestamp, the recorded time of the final GPS point, and the relative distance from the final GPS location and the accident site, it is likely that the final image from the GoPro camera depicted the canyon and wires that were struck. The airplane then impacted terrain and came to rest in a canyon about 900 ft from the location where the power lines crossed the canyon. A large portion of power line cable was found wrapped around the engine's crankshaft about 15 times, indicating that the engine was operating at considerable power output when the impact occurred.
Toxicological testing showed the presence of tetrahydrocannabinol (THC), the primary psychoactive compound in marijuana, as well as the inactive metabolites of cocaine in the pilot's blood and urine specimens. No active cocaine was found in the pilot's blood specimens, so it is unlikely that the pilot was impaired by cocaine. Although the pilot likely had a low level of active THC in his system, it is unlikely that impairment from this low level of THC contributed to the circumstances of this accident. Thus, the available evidence indicated that the pilot intentionally conducted low-level flight through a canyon without recognizing that power lines crossed the canyon, which led to the airplane's impact with power lines and subsequent impact with terrain.
Probable cause
The pilot's reckless decision to conduct low-level flight over a canyon, resulting in the airplane's impact with power lines and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18FA227
- Event ID
- 20180615X31415
- Case number
- CEN18FA227
- 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: 0fb8aeae77c644fba885c4f123494b1854945216e137b5e752dda3236b7add91; retrieved 2026-09-15T06:42:40.498Z.