- Date
- June 28, 2014, 10:40 local (14:40 UTC)
- Place
- Danbury, CT
- Injuries
- 3 uninjured
- Damage
- Substantial damage
- Phase of flight
- Standing
- Aircraft
- N7867GCessna 172L
- Defining event
- Standing-engine(s) start-up: Ground collision
- Weather
- Visual (VMC) · Day
- Status
- Completed · report October 9, 2014
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20140628012071A
- Case key
- 89559
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 use of a person unfamiliar with aviation and his failure to properly secure the airplane during hand starting of the engine.
Findings · 5
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 following preflight inspection of the airplane he attempted to start the engine using the starter but was unable. He indicated this to be, "an on-and-off issue…" in that he had to hand start the engine once during 5 attempts prior to 5 separate flights the previous weekend. He elected to hand start the engine without assistance because he was unable to locate personnel from the fixed base operator, and asked the non-rated passenger seated in the right front seat to apply the aircraft's brakes. With the airplane unsecured and the throttle applied "a little bit", the engine started. Initially the airplane did not move, but then began to move. He attempted to board the airplane but was unable and it began travelling faster. The airplane turned to the left, went between 2 rows of airplanes and impacted several parked unoccupied airplanes. The pilot further stated that he did not show the passenger how to activate the aircraft's brakes, and believes the passenger may have inadvertently applied left rudder in an attempt to stop the airplane, although the passenger told him he did not recall doing so. There were no injuries to the front or rear seat passengers, and there were no ground injuries. The Federal Aviation Administration (FAA) Pilot's Handbook of Aeronautical Knowledge contains a section titled, "Hand Propping" which indicates to never allow a person unfamiliar with the controls to occupy the pilot's seat when hand propping. The section also indicates that an additional precaution includes placement of chalks in front of the main tires or if not feasible, the airplane's tail may be securely tied. The excerpts are contained in the NTSB public docket.
Factual narrative
The pilot stated that following preflight inspection of the airplane he attempted to start the engine using the starter but was unable. He indicated this to be, "an on-and-off issue…" in that he had to hand start the engine once during 5 attempts prior to 5 separate flights the previous weekend. He elected to hand start the engine without assistance because he was unable to locate personnel from the fixed base operator, and asked the non-rated passenger seated in the right front seat to apply the aircraft's brakes. With the airplane unsecured and the throttle applied "a little bit", the engine started. Initially the airplane did not move, but then began to move. He attempted to board the airplane but was unable and it began travelling faster. The airplane turned to the left, went between 2 rows of airplanes and impacted several parked unoccupied airplanes.The pilot further stated that he did not show the passenger how to activate the aircraft's brakes, and believes the passenger may have inadvertently applied left rudder in an attempt to stop the airplane, although the passenger told him he did not recall doing so. There were no injuries to the front or rear seat passengers, and there were no ground injuries. The Federal Aviation Administration (FAA) Pilot's Handbook of Aeronautical Knowledge contains a section titled, "Hand Propping" which indicates to never allow a person unfamiliar with the controls to occupy the pilot's seat when hand propping. The section also indicates that an additional precaution includes placement of chalks in front of the main tires or if not feasible, the airplane's tail may be securely tied. The excerpts are contained in the NTSB public docket.
Aircraft
- Registration
- N7867G
- Reported as
- Cessna 172L
- Category
- Airplane
- Serial number
- 17259567
- Built
- 1970
- Airframe hours
- 5,460
- Engine
- Lycoming 0-320-E2D, 150 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- Jao-Shiang Luo
- Registered owner
- Mei-Chu Corp
- Airworthiness certificate
- Standard, Utility; Standard, Normal
- Last inspection
- Annual · February 11, 2014 · 21 hours before
- Departed
- DXR · Danbury, CT
- Destination
- MVY · Vineyard Haven, MA
- Flight plan
- VFR
- Airport
- DXR · Danbury Municipal Airport
- Equipment
- Stall warning system
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
- 51
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, With waivers/limitations
- Last flight review
- March 31, 2013
- Seat
- None
- Flight hours
- 290 total · 235 in this make and model · 149 as pilot in command · 14 in the last 90 days · 3 in the last 30 days · 0 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 220° at 3 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 79 °F, dew point 57 °F
- Altimeter
- 30.29 inHg
- Observed at
- DXR
Docket · 6
The files NTSB released with the investigation on October 2, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 6.4 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.
Other investigations on N7867G · 1
Matched to the same aircraft by N-number and date.