The U.S. aircraft register, updated daily
Accidents · NTSB FTW96LA033 · Final report

Cessna 172 accident near Oklahoma City, Oklahoma, November 2, 1995

On November 2, 1995 at about 11:33 pm local time, a Cessna 172, registered N6364E, was substantially damaged in an accident near Oklahoma City, Oklahoma. It was an instructional flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The student pilot's failure to use carburetor heat resulting in loss of engine power due to carburetor icing. A factor was the lack of suitable terrain for a forced landing.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 2, 1995 · about 11:33 pm local time
Place
Oklahoma City, Oklahoma · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 · all 172s on the register
Registration
N6364E · no longer on the register · serial 46464
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The student pilot took off, with full fuel in the left tank and 1/4 fuel in the right tank, to practice touch-and-go landings at a nearby airport. He was returning to Will Rogers World Airport approximately 1 hour later when the engine 'quit' approximately 5 miles west of the destination. He reports that he flew the whole flight with the fuel selector on the left fuel tank. He restarted the engine, but it 'quit' again about 1 mile west of runway 35L. The pilot further stated that he never used carburetor heat. During the landing roll in a field, the airplane hit a 'small gully,' nosed over, and came to rest in the inverted position. According to the carburetor icing probability chart the weather conditions at the time of the accident were conducive to the formation of carburetor ice. Additionally, the engine was test run and found to have no mechanical anomalies. Repeated attempts to obtain a completed Pilot/Operator Report of the accident from the student pilot were unsuccessful.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: student
  • Flight time: 15 hours in all
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 2,530 hours
  • Last inspection: 100-hour inspection, October 3, 1995; 3 hours since
  • Maximum gross weight: 2,300 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental O-300-A (piston); 0 hours total

The flight

  • Departed from: OKC OK at 10:30 pm
  • Flight plan: none
  • Runway 0

Weather at the time

  • Light: daylight
  • Wind: from 350° at 17 knots
  • Visibility: 10 statute miles
  • Sky: scat at 2,900 ft
  • Temperature: 39°F (4°C), dew point 27°F (-3°C)
  • Altimeter: 30.00 inHg
  • Observation at 10:56 pm from OKC, 3 miles away

Injuries

FatalSeriousMinorNone
Crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.