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

Cessna 152 accident near Farmingdale, New York, April 6, 1996

On April 6, 1996 at about 9:45 pm local time, a Cessna 152, registered N67562, was substantially damaged in an accident near Farmingdale, New York (Republic airport). It was a personal 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

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
April 6, 1996 · about 9:45 pm local time
Place
Farmingdale, New York · Republic · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 152 · all 152s on the register
Registration
N67562 · no longer on the register · serial 15281912
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that she was in an extended traffic pattern for runway 19. During the turn to final, about 10 miles from the airport, the tower controller instructed her to overfly the airport. She added power and climbed to 2000 feet, still heading toward the airport. About 2 miles from the approach end of runway 19, the tower controller then cleared her to land. The pilot reduced the power, applied carburetor heat, and established a descent towards the airport. On short final, about 200 feet above the ground, the tower controller instructed her to go around. She tried to apply power; however, the engine did not respond. She observed the tachometer was indicating about 1000 RPM, and the mixture was rich. The pilot performed a forced landing during which the airplane impacted a tree and slid into a fence. Examination of the aircraft did not disclose evidence of mechanical malfunction. A functional check of the engine revealed satisfactory operation.

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: private
  • Ratings: single-engine land
  • Flight time: 119 hours in all; 112 in this make and model; 16 in the last 90 days; 9 in the last 30 days; 23 as pilot in command
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 6,110 hours
  • Last inspection: 100-hour inspection, December 27, 1995; 60 hours since
  • Maximum gross weight: 1,670 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235-L2C (piston); 0 hours total

The flight

  • Departed from: FRG at 8:15 pm
  • Destination: FRG
  • Flight plan: none
  • Runway 19, 5,516 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 150° at 8 knots
  • Visibility: 25 statute miles
  • Sky: broken clouds at 25,000 ft; scat at 7,000 ft
  • Temperature: 45°F (7°C), dew point 0°F (-18°C)
  • Altimeter: 29.00 inHg
  • Observation at 9:37 pm from FRG

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.