Piper PA-28-161 accident near Melbourne, Florida, February 26, 2009
On February 26, 2009 at about 7:00 pm local time, a Piper PA-28-161, registered N616FT, was substantially damaged in an accident during landing (flare/touchdown) near Melbourne, Florida (Melbourne International Airpor airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The student pilot's inadequate crosswind landing technique and the certified flight instructor's delayed remedial action, which resulted in a hard landing.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 26, 2009 · about 7:00 pm local time · cases in 2009
- Place
- Melbourne, Florida · Melbourne International Airpor · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-161 · all PA-28-161s on the register
- Registration
- N616FT · no longer on the register · serial 2841239
- 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, the purpose of the instructional flight was to practice crosswind landings. The flight was to be the student pilot's last flight in preparation for his first solo flight. The certified flight instructor (CFI) who was giving the instruction reported that the airplane was landed hard with a side load. Inspection of the airplane after the flight revealed a crack in the right wing’s rear spar. The student pilot reported that there were no mechanical malfunctions with the airplane during the flight.
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
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot
- cause Personnel issues › Action/decision › Action › Delayed action › Instructor/check pilot
Flight instructor
- Certificate: flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 1,410 hours in all; 1,068 on instruments
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: rgt
- Injury: no injuries
Dual student
- Certificate: student
- Flight time: 33 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 13,197 hours
- Last inspection: 100-hour inspection, January 26, 2009; 100 hours since
- Maximum gross weight: 2,447 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-D3G (piston); 0 hours total
- Operator: F I T Aviation LLC
The flight
- Departed from: MLB Melbourne FL at 1:00 pm
- Destination: MLB Melbourne FL
- Flight plan: none
- Runway 05, 3,001 ft by 75 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 100° at 10 knots
- Visibility: 10 statute miles
- Sky: scat at 4,000 ft
- Temperature: 72°F (22°C), dew point 48°F (9°C)
- Altimeter: 30.27 inHg
- Observation at 6:53 pm from MLB
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
4 documents, released by the NTSB on April 26, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 - Operator | PDF, 9 pages | View Download |
| 2 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 - Student Pilot | PDF, 9 pages | View Download |
| 3 | Florida Institute of Technology Malfunction Report | PDF, 1 page | View Download |
| 4 | Florida METAR Observations | PDF, 6 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N616FT the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N616FT: not on the register today · the record of its deregistration
- Piper PA-28 Cherokee, Warrior, Archer and Arrow 18,620 registered today · the model family and its accident history
- Piper 44,844 aircraft on the register
- Engine: Lycoming O-320-D3G 133 aircraft carry this series today · as the NTSB recorded it
- Melbourne Orlando International · nearest airport
- Accidents and incidents in Florida 6,111 since 1982 · 982 in the last ten years
- Florida 21,718 aircraft registered
- Other NTSB records under N616FT 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/ERA11LA067.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
