- Date
- August 2, 2013, 23:20 local (Aug 3, 2013, 03:20 UTC)
- Place
- Portsmouth, NH
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N645PDCessna 172S
- Defining event
- Initial climb: Loss of control in flight
- Weather
- Visual (VMC) · Night
- Status
- Completed · report September 12, 2013
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20130803016509A
- Case key
- 87686
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot’s inadequate preflight inspection resulting in his failure to remove the pin he used to lock the flight controls in place of the approved control lock.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The pilot stated that in preparation for a night flight, he flew earlier that same evening. He inspected the airplane and noted the control lock was not installed in the control column. While searching for the control lock he located a “straight pin” in a seatback pocket and installed it. He left the airport and returned later than evening, and performed a preflight inspection of the airplane removing the straight pin. He departed and flew to his destination airport where he landed uneventfully. After landing he went to a fixed base operator and filed a flight plan for the return flight, then returned to the airplane and started the engine. He taxied to the run-up area of runway 34 where he performed the before takeoff checklist but did not check that the flight controls were free and clear for fear of having his tablet knocked off the yoke mount. He advised the controller that he was ready for departure and was cleared for takeoff. He taxied onto the runway and applied power noting the airspeed increased normally. After the airplane rotated it climbed to an altitude of about 3 feet and settled back down on the runway and bounced. Confused as to what was occurring, he added nose up trim to assist in the climb. At this point the airplane climbed to about 10 feet, then the nose pitched downward and the nose wheel struck the runway. After coming to a stop he switched the headlamp he was wearing from red to white and noticed the pin used to secure the flight controls was in the control lock hole. He removed the pin and retained possession of it. Post accident inspection of the airplane by a FAA inspector revealed substantial damage to the firewall.
Factual narrative
The pilot stated that in preparation for a night flew earlier that same evening, he inspected the airplane and noted the control lock was not installed in the control column. While searching for the control lock he located a “straight pin” in a seatback pocket and installed it. He left the airport and returned later than evening, and performed a preflight inspection of the airplane removing the straight pin. He departed and flew to his destination airport where he landed uneventfully. After landing he went to a fixed base operator and filed a flight plan for the return flight, then returned to the airplane and started the engine. He taxied to the run-up area of runway 34 where he performed the before takeoff checklist but did not check that the flight controls were free and clear for fear of having his tablet knocked off the yoke mount. He advised the controller that he was ready for departure and was cleared for takeoff. He taxied onto the runway and applied power noting the airspeed increased normally. After the airplane rotated it climbed to an altitude of about 3 feet and settled back down on the runway and bounced. Confused as to what was occurring, he added nose up trim to assist in the climb. At this point the airplane climbed to about 10 feet, then the nose pitched downward and the nose wheel struck the runway. After coming to a stop he switched the headlamp he was wearing from red to white and noticed the pin used to secure the flight controls was in the control lock hole. He removed the pin and retained possession of it. Post accident inspection of the airplane by a FAA inspector revealed substantial damage to the firewall.
Aircraft
- Registration
- N645PD
- Reported as
- Cessna 172S
- Category
- Airplane
- Serial number
- 172S8644
- Airframe hours
- 5,398
- Engine
- Lycoming I0-360-L2A, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- Westfield Flight Academy
- Registered owner
- Climb On LLC
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · June 19, 2013 · 59 hours before
- Departed
- PSM · Portsmouth, NH
- Destination
- BAF · Westfield, ME
- Flight plan
- IFR
- Airport
- PSM · Portsmouth Intn'l Airport, runway 34, 11,321 × 150 ft, asphalt
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 33
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, Without waivers/limitations
- Last flight review
- March 21, 2013
- Seat
- Left
- Flight hours
- 204 total · 149 in this make and model · 108 as pilot in command · 13 in the last 90 days · 6 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Night
- Wind
- 230° at 3 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- 12,000 ft overcast
- Temperature
- 68 °F, dew point 57 °F
- Altimeter
- 29.82 inHg
- Observed at
- PSM
Docket · 9
The files NTSB released with the investigation on September 4, 2013, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.8 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.