Cessna 172 accident near Farmingdale, New York, March 21, 2010
On March 21, 2010 at about 3:45 pm local time, a Cessna 172, registered N1895A, was substantially damaged in an accident during landing (flare/touchdown) near Farmingdale, New York (Republic 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 student pilot's improper flare and recovery from a bounced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 21, 2010 · about 3:45 pm local time
- Place
- Farmingdale, New York · Republic Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172 S · all 172s on the register
- Registration
- N1895A · no longer on the register · serial 172S9933
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the student pilot, while returning from his first solo cross-country flight the airplane landed flat and porpoised. After several bounces, the nose landing gear collapsed and the propeller struck the runway. The airplane came to a stop after the student pilot steered it onto a taxiway. The student pilot reported a total flight experience of 34 hours, and that there were no mechanical problems with the airplane. Variable winds at 5 knots were present at the time of the accident.
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
- Hard landing during landing (flare/touchdown) defining event
- Landing gear collapse during landing (flare/touchdown)
- Abnormal runway contact during landing (flare/touchdown)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
Dual student
- Certificate: student
- Flight time: 34 hours in all; 34 in this make and model
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,556 hours
- Last inspection: 100-hour inspection, February 28, 2010; 43 hours since
- Maximum gross weight: 2,558 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360 (piston); 0 hours total
- Operator: Academy Of Aviation
The flight
- Departed from: GON Groton CT at 2:50 pm
- Destination: FRG Farmingdale NY
- Flight plan: none
- Runway 14, 6,827 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 55°F (13°C), dew point 43°F (6°C)
- Altimeter: 30.11 inHg
- Observation at 3:53 pm from FRG
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.