CEN22LA414 · Cessna 172M
Journeys Aviation Cessna 172M · Accident: low altitude operation/event while maneuvering
From Boulder Municipal Airport (KBDU) to an unrecorded destination
Event
- NTSB case
- CEN22LA414
- 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
- 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 172M
- 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
- N9049H
- Operator
- Journeys Aviation
- Onboard fatalities
- Unknown
- Route
- From Boulder Municipal Airport (KBDU), Boulder, COTo not recorded
- Aircraft age
- About 47 years (built 1975)
- 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 · low-altitude flying
- 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
- Low altitude operation/event
- 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
- 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
A pilot and flight instructor were conducting a personal flight over a reservoir when they descended and flew at a low altitude over two boats on the water. After passing the second boat, they turned west into a cove and impacted rising terrain about 1 mile west of the shoreline, which resulted in substantial damage to the fuselage and both wings. Following the accident, the flight instructor made differing and conflicting statements to the National Transportation Safety Board (NTSB). The first statement was that there was an engine malfunction and to avoid landing on the water or impacting boats on the surface, he elected to make a climbing right turn to the west, away from the lake, and the airplane subsequently impacted rising terrain. In a written statement provided by the flight instructor, he stated that the power had been reduced to “see more of the scenery.” Shortly thereafter, the pilot flying told him that he could not climb due to a jammed elevator. The flight instructor stated that he could only control the airplane through the use of trim and power manipulation. To avoid congested areas, they maneuvered to the reservoir and attempted to free the jammed elevator by “wiggling the flight control in and out,” which resulted in the airplane pitching down. He stated that after adding power and retrimming the airplane, he elected to fly west into the valley to look for a landing area. A review of flight track data revealed that the airplane did not descend as described in the written statement, but instead flew east to west over the reservoir and descended during a 270° turn over the reservoir that was initiated about mid-channel. The airplane traversed about 1.6 miles south along the reservoir before it turned west and climbed. The last recorded altitude was about 6,075 ft msl near the accident location. Photographs provided by a witness show the airplane low over the water as it approached one of only three visible boats. At first, the airplane appeared headed toward the shore, but made a left turn toward the first boat. After making a very low pass over the boat, the airplane made a steep climb, followed by a steep right turn, and then flew at a low altitude over the second boat. After passing the second boat, the airplane appeared to depart toward a valley. Postaccident examinations by the Federal Aviation Administration and the NTSB revealed no mechanical malfunctions or anomalies that would have precluded normal operation of the engine or flight controls.
Probable cause
The pilot’s failure to maintain clearance from rising terrain while intentionally maneuvering the airplane at low altitudes, which resulted in substantial damage to the fuselage and both wings.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA414
- Event ID
- 20220912105911
- Case number
- CEN22LA414
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2022-09-12.
- API snapshot SHA-256: 12cebb2ed42d79d74951ea07520115ec3064f61e4f108610a368698c62a9f3af; retrieved 2026-09-16T15:59:04.114Z.