ERA15LA294

NTSB accident investigation · Commander 114 · Reading, PA · August 1, 2015

Accident · No injuriesLimited investigationFinal report
Date
August 1, 2015, 13:19 local (17:19 UTC)
Place
Reading, PA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N6566DCommander 114
Defining event
Enroute-cruise: Loss of engine power (total)
Weather
Visual (VMC) · Day
Status
Completed · report March 14, 2016
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20150801023819A
Case key
91698

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 improper installation of the fuel supply line fitting at the fuel manifold, which resulted in the line loosening in-flight, fuel leakage, and a subsequent total loss of engine power.

Findings · 4

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.

Engine fuel and controlAircraft › Aircraft power plant · Incorrect service/maintenanceCommander 114-B: 1 caseAll aircraft: 49 casesProbable cause
Maintenance: installationPersonnel issues › Task performance · Maintenance personnelCommander 114-B: 1 caseAll aircraft: 371 casesProbable cause
Terrain: rough terrainEnvironmental issues › Physical environment · Contributed to outcomeCommander 114-B: 1 caseAll aircraft: 442 cases
Object/animal/substance: tree(s)Environmental issues › Physical environment · Contributed to outcomeCommander 114-B: 1 caseAll aircraft: 933 cases

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

According to the airline transport pilot, about 30 minutes into the personal flight and while the airplane was at 3,000 ft mean sea level, the engine "seemed to lose power for a second." About 1 second later, the engine "shut off completely." The pilot tried to restart the engine by turning on the electric fuel boost pump and then moving the fuel selector to each of the positions without success. He then moved the fuel selector back to the "both tanks" position and set the nose pitch for best glide speed; however, the airplane was unable to glide to the airport, so the pilot set it up for an off-field landing. During the forced landing, the airplane encountered uneven terrain, and the right wing struck a tree. A postaccident engine test run was conducted, and the engine would not start. Subsequent examination of the engine revealed that a fuel supply line fitting at the fuel manifold was loose and that fuel leaked excessively from the fitting when the electric boost pump was turned on. After the fitting was tightened, the engine started without hesitation and ran continuously at idle power. Due to three bent propeller blades and vibration, a higher power setting was not attempted. A review of the airplane and engine logbooks found no entries indicating that any recent maintenance had been conducted on the fuel system.

Factual narrative

On August 1, 2015, about 1319 eastern daylight time, a Commander Aircraft Company 114-B, N6566D, was force landed following a reported loss of engine power during cruise flight near Reading, Pennsylvania. The airline transport-rated pilot and a private pilot-rated passenger were not injured, and the airplane was substantially damaged. The airplane was registered to Precision Machine Tool Solutions LLC and was operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. Day, visual meteorological conditions prevailed, and no flight plan was filed. The local flight originated at Reading Regional Airport (RDG), Reading, Pennsylvania about 1250. The airline transport-rated pilot, who reported that he was the pilot-in-command, seated in the right, cockpit seat, reported the following. About 30 minutes into the flight, at 3,000 feet above mean sea level, while returning to RDG, the engine "seemed to lose power for a second." About 1 second later, the engine "shut off completely." He assumed the controls and immediately began to accomplish the engine failure procedures. He turned on the electric boost pump and moved the fuel tank selector to all positions; the engine would not restart. He returned the selector to the "both tanks" position and set the nose pitch for best glide speed. He called RDG approach control and advised them of the situation. Unable to glide to the airport, he set up for an off-field landing. During the forced landing, undulating terrain was encountered, and the right wing struck a tree. The airplane came to a stop in a vegetable garden and both occupants exited the cockpit. An inspector with the Federal Aviation Administration (FAA) responded to the accident site and examined the wreckage. The fuselage, empennage, and left wing exhibited structural damage from impact forces. The right wing was sheared off at the root. Both wing tanks contained fuel, and there was evidence of fuel leakage at the accident site. The wreckage was recovered and moved to a recovery facility for further examination. On September 16, 2015, the engine was examined by an investigator from the NTSB and an inspector from the FAA. The wings had been removed from the airplane for transport to the recovery facility. The remaining fuselage was secured to a flatbed trailer for an engine test-run. Fuel was supplied via a 5-gallon container to the right wing side of the fuel selector. During the first attempt, the engine did not start. Subsequent examination of the engine revealed a loose fitting that connected the fuel supply line to the fuel manifold, with fuel leaking from the fitting when the auxiliary fuel pump was activated. The fitting was tightened and the engine then started on the first attempt without hesitation and ran continuously at idle power. Due to three bent propeller blades and vibration, a higher power setting was not attempted. A review of the maintenance records for the airframe and enginerevealed no evidence of recent maintenance on the fuel system. The most recent inspection was an annual inspection, completed on January 1, 2015. During that inspection, a pressure test of the fuel system was recorded. At the time of the accident, the engine had accrued 56 hours of operating time since the annual inspection of January 1.

Aircraft

Registration
N6566D
Reported as
Commander 114 (B)
Category
Airplane
Serial number
14671
Built
2000
Airframe hours
1,091
Engine
Lycoming IO-540-T4B5, 260 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · January 1, 2015 · 56 hours before
Departed
RDG · Reading, PA
Destination
RDG · Reading, PA
Airport
RDG · Reading Regional Airport
Equipment
Stall warning system, ADS-B, Auto-pilot, Onboard weather

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 · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot-rated passenger
Age
56
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Seat
Left
Restraint
3-point
Flight hours
327 total
Role
Pilot
Age
47
Injuries
None
Certificates
Commercial, Airline transport, Private, Flight instructor
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 1, Without waivers/limitations
Last flight review
September 1, 2014
Seat
Right
Restraint
3-point
Flight hours
3,700 total · 546 in this make and model · 2,680 as pilot in command · 191 in the last 90 days · 80 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
260° at 10 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
86 °F, dew point 54 °F
Altimeter
29.84 inHg
Observed at
RDG, 4 nm away

Docket · 5

The files NTSB released with the investigation on January 29, 2016, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.6 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.