CEN10CA532 · Robertson VELOCITY
Robertson VELOCITY · Accident: loss of engine power (total) while maneuvering
From Somerset County Airport (2G9) to Wayne County Airport (BJJ)
Event
- NTSB case
- CEN10CA532
- 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
Robertson VELOCITY
- Aircraft type
- Robertson VELOCITY
- 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
- N112TH
- Operator
- Robertson James F
- Onboard fatalities
- Unknown
- Route
- From Somerset County Airport (2G9), Somerset, PATo Wayne County Airport (BJJ), Wooster, OH
- Aircraft age
- Not recorded
- 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
- Loss of engine power (total)
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, prior to departure, the fuel system sight gages indicated he had over 25 gallons of fuel on board; he did not visually check the fuel level in the tanks. Upon reaching his destination, the pilot made a low approach over the runway, climbed, and flew to an area about 5 miles from the airport to wait for another airplane to land ahead of him. The engine experienced a loss of power and he maneuvered the airplane into a glide back to the airport. Realizing he was not going to be able to reach the airport, the pilot chose a field to perform a forced landing. Just prior to touch down, the airplane stalled and landed hard. Postaccident inspection of the airplane revealed the fuel tanks were intact and there was no fuel present either in the tanks or on the ground around the wreckage.
Probable cause
A loss of engine power due to fuel exhaustion as a result of the pilot's inadequate fuel planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA532
- Event ID
- 20100910X52812
- Case number
- CEN10CA532
- 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. 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: 89591676ebb99d9a5c398717211f2a82106a870cf662cacdb1ad9e972d6e718f; retrieved 2026-09-15T15:09:27.409Z.