GAA18CA135 · Cessna 172 M
Bell Ornithopters Flying Club Cessna 172 M · Accident: loss of control on ground during landing
From Vance Brand Airport (LMO) to Rocky Mountain Metropolitan Airport (BJC)
Event
- NTSB case
- GAA18CA135
- 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
- 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 172 M
- 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
- N13453
- Operator
- Bell Ornithopters Flying Club
- Onboard fatalities
- Unknown
- Route
- From Vance Brand Airport (LMO), Longmont, COTo Rocky Mountain Metropolitan Airport (BJC), Broomfield, CO
- Aircraft age
- About 45 years (built 1973)
- 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
- Landing · landing roll
- 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
- Loss of control on ground
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the landing roll on runway 30, about 10 miles per hour, in gusting wind conditions, the airplane exited the right side of the runway and collided with a drainage culvert and nosed over.
The airplane sustained substantial damage to the left-wing lift strut, the rudder and the vertical stabilizer.
The METAR at the accident airport reported that about the time of the accident, the wind was from 240° at 27 kts and gusting to 40 kts.
The manufacturer's pilot operating handbook specified that the maximum demonstrated crosswind component during takeoff or landing was 15 knots. The calculated crosswind component for the specified conditions was 29 knots.
The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control of the airplane during the landing roll in gusting wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA135
- Event ID
- 20180217X03946
- Case number
- GAA18CA135
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2018-02-17.
- API snapshot SHA-256: d8d22b8b7951ba5e153e776a41d0ef09c3798f212bf3d60e863d58c577c56ffc; retrieved 2026-09-16T06:29:22.408Z.