OpenAirDocs.org

20080630842949I

Incident · Minor damage
Open the Markdown

FAA incident report · Beech 95 · Rochester, NH · June 30, 2008

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
June 30, 2008 · 19:30 local
Place
Rochester, NH
Airport
Skyhaven
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N2715Y
Reported as
Beech 95
People aboard
2
Fatal injuries
0
Pilot’s flight hours
26,000 total200 in this make and model5 in the last 90 days
N2715YRegistered now · Beech 95S/N TD-62 · Built 1958Airframe modelBeech 95Engine modelLycoming O&VO-360 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) Due to a previous incident in which privacy data omitted was involved, he was under a requirement to submit to a reexamination of his pilot abilities. Pursuiant to this requirement privacy data omitted obtained the services of a multiengine CFI to accompany him in preparation for the reexamination. After takeoff and during the initial climb out from the Rochester, NH airport, the caibn door sprung open, necessitating a return back to the airport for landing. The instructor privacy data omitted took over the controls as privacy data omitted had no lined up properly with the runway and made a successful landing on the beginning of the runway. As there are only one set of brake controls, (on the left side pilot position), the CFI returned the aircraft operations back to privacy data omitted. privacy data omitted Was advised several times by the CFI to apply braking action, but there was no response from the pilot. The aircraft subsequently left the departure end of the runway, incuring a propeller strike on a runway light and coming to a stop approximatley 80 feet from the runway.

As the FAA filed it

(-23) DUE TO A PREVIOUS INCIDENT IN WHICH ^PRIVACY DATA OMITTED^ WAS INVOLVED, HE WAS UNDER A REQUIREMENT TO SUBMIT TO A REEXAMINATION OF HIS PILOT ABILITIES. PURSUIANT TO THIS REQUIREMENT ^PRIVACY DATA OMITTED^ OBTAINED THE SERVICES OF A MULTIENGINE CFI TO ACCOMPANY HIM IN PREPARATION FOR THE REEXAMINATION. AFTER TAKEOFF AND DURING THE INITIAL CLIMB OUT FROM THE ROCHESTER, NH AIRPORT, THE CAIBN DOOR SPRUNG OPEN, NECESSITATING A RETURN BACK TO THE AIRPORT FOR LANDING. THE INSTRUCTOR ^PRIVACY DATA OMITTED^ TOOK OVER THE CONTROLS AS ^PRIVACY DATA OMITTED^ HAD NO LINED UP PROPERLY WITH THE RUNWAY AND MADE A SUCCESSFUL LANDING ON THE BEGINNING OF THE RUNWAY. AS THERE ARE ONLY ONE SET OF BRAKE CONTROLS, (ON THE LEFT SIDE PILOT POSITION), THE CFI RETURNED THE AIRCRAFT OPERATIONS BACK TO ^PRIVACY DATA OMITTED^. ^PRIVACY DATA OMITTED^ WAS ADVISED SEVERAL TIMES BY THE CFI TO APPLY BRAKING ACTION, BUT THERE WAS NO RESPONSE FROM THE PILOT. THE AIRCRAFT SUBSEQUENTLY LEFT THE DEPARTURE END OF THE RUNWAY, INCURING A PROPELLER STRIKE ON A RUNWAY LIGHT AND COMING TO A STOP APPROXIMATLEY 80 FEET FROM THE RUNWAY.