CEN14CA469 · Cirrus Design Corp SR22
Bobnruth Services Cirrus Design Corp SR22 · Accident: loss of control in flight on approach
From North Las Vegas Airport (VGT) to Granby Grand County Airport (GNB)
Event
- NTSB case
- CEN14CA469
- 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
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- 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
- N224BR
- Operator
- Bobnruth Services
- Onboard fatalities
- Unknown
- Route
- From North Las Vegas Airport (VGT), North Las Vegas, NVTo Granby Grand County Airport (GNB), Granby, CO
- Aircraft age
- About 8 years (built 2006)
- 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
- Approach · VFR go-around
- 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 in flight
- 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
- Personnel issues › Task performance
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 reported he was not comfortable with his altitude and airspeed while landing on runway 9, so he elected to perform a go-around. When he added power for the go-around, the airplane rolled to the left. The pilot attempted to recover from the roll, but the airplane contacted an eight foot tall airport perimeter fence and a road on the north side of the runway. The airplane came to rest inverted in a field adjacent to the road. The fuselage and wings of the airplane sustained substantial damage. The pilot reported the local wind was from 210 degrees at 5 knots. Precision approach indicator lights (PAPI) were installed and operating on runway 9 at the time of the accident. The fence that was contacted by the airplane was measured to be 214 feet from the edge of the runway.
Probable cause
The pilot did not maintain control of the airplane during the go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA469
- Event ID
- 20140901X92912
- Case number
- CEN14CA469
- 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: 26bb433b3cd0bed65bc77a859d3971ee626185f4ff8bb89b3b754ba17f469e4a; retrieved 2026-09-16T01:42:17.728Z.