Cessna 172M accident near Princeton, New Jersey, July 4, 2009
On July 4, 2009 at about 2:45 pm local time, a Cessna 172M, registered N64178, was substantially damaged in an accident during approach (VFR pattern base) near Princeton, New Jersey (Princeton Airport). 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 partial loss of engine power for undetermined reasons.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 4, 2009 · about 2:45 pm local time
- Place
- Princeton, New Jersey · Princeton Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172M · all 172Ms on the register
- Registration
- N64178 · no longer on the register · serial 17265067
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student pilot stated that he was in the traffic pattern practicing touch-and-go landings. As he turned base, the engine went to idle, and he made an emergency landing in a field. The carburetor heat was in use at the time of engine failure. Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that the flight control system components, engine, and system components revealed no evidence of preimpact mechanical malfunction. The current ambient temperature was 75 degrees Fahrenheit, with a dew point of 55 degrees Fahrenheit. Review of the carburetor icing probability chart revealed that serious carburetor icing could occur at glide power.
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
What happened, in order
- Loss of engine power (total) during approach (VFR pattern base) defining event
- Off-field or emergency landing during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: student
- Flight time: 30 hours in all
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 5,774 hours
- Last inspection: annual inspection, May 5, 2009; 13 hours since
- Maximum gross weight: 2,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320 SERIES (piston); 0 hours total
The flight
- Departed from: 39N Princeton NJ at 2:40 pm
- Destination: 39N Princeton NJ
- Flight plan: none
- Runway 28, 3,499 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 310° at 9 knots, gusting 15
- Visibility: 10 statute miles
- Sky: a few clouds at 4,500 ft
- Temperature: 75°F (24°C), dew point 55°F (13°C)
- Altimeter: 29.88 inHg
- Observation at 2:53 pm from TTN
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
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.