- Date
- March 13, 2010, 18:00 local (Mar 14, 2010, 00:00 UTC)
- Place
- Ninnekah, OK
- Injuries
- 4 minor
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N4974FCessna TU206
- Defining event
- Enroute-climb to cruise: Fuel exhaustion
- Weather
- Visual (VMC) · Day
- Status
- Completed · report February 6, 2012
- Report
- Approved by Office Director
- NTSB office
- Central Region
- Parties
- Continental Motors, FAA Oklahoma City FSDO
- FAA report
- 20100313029499A
- Case key
- 75505
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
A loss of engine power due to fuel exhaustion, resulting from the pilot’s inadequate preflight inspection.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
Shortly after departure and on the downwind leg of the traffic pattern, the engine lost power. The pilot tried to make a forced landing on the runway, but the airplane collided with terrain short of the runway. During the impact the airplane struck a berm and nosed over, which resulted in substantial damage to the fuselage, empennage, vertical fin, rudder, and both wings. According to the passengers, the purpose of the flight was to obtain fuel from another airport, and, during takeoff, the fuel gauges appeared to indicate empty. The pilot did not perform a preflight inspection; he told the passengers that he had enough fuel for the 5-minute flight. A postaccident examination of the engine and related systems revealed no preimpact anomalies.
Factual narrative
On March 13, 2010, about 1800 central standard time, a Cessna TU206/B airplane, N4974F, was substantially damaged during a forced landing following a loss of engine power at Neil’s Sky Ranch Airport (O14), Ninnekah, Oklahoma. The pilot and the three passengers sustained minor injuries. The airplane was owned by Advanced Aviation, LLC and was operated by the pilot. Visual meteorological conditions prevailed at the time of the accident and a flight plan had not been filed for the 14 Code of Federal Regulations Part 91 personal flight. The airplane had departed O14 and was en route to Chickasha Municipal Airport (CHK), Chickasha, Oklahoma. Both adult passengers reported that the purpose of the flight was to fly to CHK to get fuel and quickly return to O14 before the hours of darkness. Before the flight began, the passengers had each asked the pilot if there was enough fuel to make the trip. The pilot replied there was more than enough for the 5-minute flight. One passenger reported that the pilot did not perform any kind of preflight inspection before he got in the airplane and “fired it up”. The front seat passenger noticed during takeoff that the left fuel gauge indicated empty and the right fuel gauge indicated between one eighth to one quarter. The airplane had departed to the south and was climbing northbound on a left downwind leg when the engine suddenly stopped. A passenger stated he heard the pilot say at that moment “we’re out of gas”. The pilot immediately headed toward the airport but impacted terrain off the edge of the runway. After the initial impact the airplane struck the upslope side of a berm and nosed over, coming to rest inverted near the east edge of the runway. The pilot was the first to exit the airplane and then assisted the injured front seat passenger who had been briefly unconscious. The pilot then assisted the two-year-old child and the adult passenger. The airplane was not equipped with shoulder harnesses for any seat. Because of the airplane’s year of manufacture shoulder harness installation was not required. On April 12, 2010, the airplane was examined under the supervision of a Federal Aviation Administration inspector. There was substantial damage to the fuselage, empennage, vertical fin, rudder, and both wings. Except for some damage to the rear engine mounts the engine was not impact damaged. A club propeller was installed to replace the damaged propeller, and the engine, still attached to the fuselage, was prepared for a test run. The engine was started using the airframe electrical system and was operated for about 10 minutes, including operation at full rated power. No preimpact anomalies were seen that would have prevented normal operation.
Aircraft
- Registration
- N4974F
- Reported as
- Cessna TU206 (B)
- Category
- Airplane
- Serial number
- U206-0674
- Airframe hours
- 3,103
- Engine
- Continental IO520, 285 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · March 10, 2010 · 1 hours before
- Departed
- O14 · Ninnekah, OK
- Destination
- CHK · Chickasha, OK
- Airport
- O14 · Neil's Sky Ranch Airport, runway 17, 3,000 × 150 ft, grass/turf
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 29
- Injuries
- Minor
- Certificate
- Commercial
- Airplane ratings
- Single-engine land, Single-engine sea, Multi-engine land
- Instrument ratings
- Airplane
- Medical
- Class 2, Without waivers/limitations
- Last flight review
- June 20, 2009
- Seat
- Left
- Flight hours
- 5,300 total · 50 in this make and model · 50 in the last 90 days · 10 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 20° at 6 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 57 °F, dew point 46 °F
- Altimeter
- 29.78 inHg
- Observed at
- KCHK, 12 nm away
Docket · 14
The files NTSB released with the investigation on December 14, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.3 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.