# NTSB CEN11LA568: Quad City Challenger, N979JP, Granbury, TX, August 16, 2011 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: August 16, 2011, 10:00 local (15:00 UTC) - Place: Granbury, TX - Coordinates: 32.436389, -97.807777 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.4364&lon=-97.8078&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340) - Highest injury: Serious injuries - Injuries: 2 serious - Status: Completed, report February 14, 2013 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA Cleveland FSDO, FAA Fort Worth FSDO - NTSB case key (mKey): 81482 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN11LA568 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81482/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=81482 - Page: https://openairdocs.org/ntsb/CEN11LA568 ## Probable cause The leak in the plastic connectors in the fuel lines, which resulted in decreased engine power during the initial climb. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Engine fuel and control: fuel distribution](https://openairdocs.org/ntsb-findings/01057310): Aircraft › Aircraft power plant · Fatigue/wear/corrosion (probable cause); cases with it: [Quad City Ultralights CHALLENGER II CW, 1 case](https://openairdocs.org/ntsb-findings/01057310/cases.md?model=05901XV), [All aircraft, 55 cases](https://openairdocs.org/ntsb-findings/01057310/cases.md) - [Engine (reciprocating)](https://openairdocs.org/ntsb-findings/01058500): Aircraft › Aircraft power plant · Damaged/degraded (probable cause); cases with it: [Quad City Ultralights CHALLENGER II CW, 1 case](https://openairdocs.org/ntsb-findings/01058500/cases.md?model=05901XV), [All aircraft, 497 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340) (defining event); cases with it: [Quad City Ultralights CHALLENGER II CW, 1 case](https://openairdocs.org/ntsb-events/340/sequence.md?model=05901XV), [All aircraft, 820 cases](https://openairdocs.org/ntsb-events/340/sequence.md) - [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342); cases with it: [Quad City Ultralights CHALLENGER II CW, 1 case](https://openairdocs.org/ntsb-events/342/sequence.md?model=05901XV), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md) - [Emergency descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Quad City Ultralights CHALLENGER II CW, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=05901XV), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilots noted a decrease in engine performance during the initial climb, and the airplane began to descend. The airplane subsequently stalled about 10 to 15 feet above ground level and impacted terrain. An examination of the airplane showed that plastic “Y” connectors in the fuel lines were cracked and leaking. The cracked and leaking connectors in the fuel lines would have caused decreased fuel flow to the engine and are consistent with the reported loss in engine performance. Postaccident examination revealed no other preimpact malfunctions or anomalies that would have precluded normal operation. ## Factual narrative On August 16, 2011, about 1000 central daylight time, a Quad City Challenger II CW, experimental light sport airplane, N979JP, was substantially damaged when it impacted terrain during initial climb at Granbury Regional Airport (GDJ) Granbury, Texas. The airplane was owned by a private individual and operated by another private individual. The pilot and second pilot sustained serious injuries. Visual meteorological conditions prevailed and a flight plan had not been filed for the 14 Code of Federal Regulations Part 91 personal flight. At the time of the accident the airplane was departing GDJ for a local flight. The second pilot stated that during takeoff the airplane had difficulty getting airborne and he did not think the engine ever “got up to full power”. The pilot stated that during the initial climb he detected a decrease in engine performance, but was unable to stop the descent. The airplane stalled about 10 to 15 feet above ground level. During impact the landing gear collapsed and there was substantial damage to the fuselage, engine mount, and empennage. The engine electronic control unit (ECU), wiring harness, fuel lines, and throttle body injectors were removed and examined at the engine manufacturer’s maintenance facility. The control linkage was found to be in working order with no deficiencies. The ECU also tested within design parameters with no defects noted. The fuel lines connected to the engine were examined. The rubber hoses had dry rot and both plastic “Y” connectors were observed to be cracked and leaking. During disassembly one “Y” connector broke and separated. When the second “Y” connector was tested with colored water under operating pressure fluid began to spray out of the crack. An examination of the airplane and engine found no other preimpact anomalies. The airplane was equipped with a ballistic parachute recovery system with a rocket motor activated by an emergency firing handle in the cockpit. After the wreckage had been moved to another location the emergency firing handle in the cockpit was observed to be hanging loose, unsecured, and the safety pin was not installed. Emergency responders that had assisted the two pilots at the accident scene, and the persons that moved the wreckage to the other location, were unaware of the presence of the rocket motor on the airplane and unaware that it was then armed and ready to fire. ## Aircraft - Registration: [N979JP](https://openairdocs.org/deregistered/N979JP-2014-11-25), registration cancelled 2014-11-25, S/N CH2-0699-CW-1889, built 2005 (OpenAirDocs) - Reported make and model: QUAD CITY CHALLENGER (II CW) - Registry model: [Quad City Ultralights CHALLENGER II CW](https://openairdocs.org/model/quad-city-ultralights-challenger-ii-cw) (registry code 05901XV) (OpenAirDocs) - Registry engine: [Hirth 2706](https://openairdocs.org/engine/hirth-2706) (registry code 33703, 2 cycle) (OpenAirDocs) - Category: Airplane - Serial number: CH2-0699-CW-1889 - Airframe hours: 92 - Engines: HIRTH 2706 Series 65 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental light sport (Special) - Last inspection: Condition, August 5, 2011, 0 hours before - Departed: GDJ, Granbury, TX - Destination: GDJ, Granbury, TX - Airport: GDJ, Granbury Regional Airport, runway 14, 3,603 × 60 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 62; injuries: serious; flight instructor, commercial; airplane ratings: single-engine sea, multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review February 1, 2010; seat: front; flight hours: 11,500 total, 0 in this make and model - Other flight crew; age 75; injuries: serious; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review November 1, 2010; seat: rear; flight hours: 1,600 total, 500 in this make and model, 10 in the last 90 days, 2 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 200° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 91 °F, dew point 64 °F - Altimeter: 29.95 inHg - Observed at: KGDJ ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20110816024889A](https://openairdocs.org/incident/20110816024889A), Aug 16, 2011: Quad City Ultralights CHALLENGER II CW, Granbury, TX, Substantial damage. Engine power failed on takeoff. Fuel injection problem suspected. ## Docket (14 files) The files NTSB released with the investigation on December 19, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=81482. 5.9 MB in all. - Summmary of IIC's Examination of Wreckage (item 1, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383287&FileExtension=.PDF&FileName=Summmary%20of%20IIC%27s%20Examination%20of%20Wreckage-Master.PDF - FAA Inspector's Report of Examination of Engine Components (item 2, .PDF, 3 photos, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383290&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Report%20of%20Examination%20of%20Engine%20Components-Redacted.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 3, .PDF, 745 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383269&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversations With Both Crewmembers (item 4, .PDF, 59 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383272&FileExtension=.PDF&FileName=Record%20of%20Conversations%20With%20Both%20Crewmembers-Master.PDF - Crewmember Statement - Second Pilot (item 5, .PDF, 587 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383270&FileExtension=.PDF&FileName=Crewmember%20Statement%20-%20Second%20Pilot-Redacted.PDF - Maps (item 6, .PDF, 184 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40352721&FileExtension=.PDF&FileName=Maps-Master.PDF - Photo 1 - Close view of wreckage from the right side looking aft (NTSB Photo) (item 7, .PDF, 175 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383291&FileExtension=.PDF&FileName=Photo%201%20-%20Close%20view%20of%20wreckage%20from%20the%20right%20side%20looking%20aft%20%20(NTSB%20Photo)-Master.PDF - Photo 2 - Wreckage as viewed from the left rear looking foreward (NTSB Photo) (item 8, .PDF, 167 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383294&FileExtension=.PDF&FileName=Photo%202%20-%20Wreckage%20as%20viewed%20from%20the%20left%20rear%20looking%20foreward%20%20(NTSB%20Photo)-Master.PDF - Photo 3 - Engine as viewed from the left side (NTSB Photo) (item 9, .PDF, 288 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383301&FileExtension=.PDF&FileName=Photo%203%20-%20Engine%20as%20viewed%20from%20the%20left%20side%20%20(NTSB%20Photo)-Master.PDF - Photo 4 - Precrash photo in 2008 showing the location of the BRS system components (Grant Sackel Photo) (item 10, .PDF, 291 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383302&FileExtension=.PDF&FileName=Photo%204%20-%20Precrash%20photo%20in%202008%20showing%20the%20location%20of%20the%20BRS%20system%20components%20%20(Grant%20Sackel%20Photo)-Master.PDF - Photo 5 - Close view of the BRS components mounted on the top surface of the wing (NTSB Photo) (item 11, .PDF, 451 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383303&FileExtension=.PDF&FileName=Photo%205%20-%20Close%20view%20of%20the%20BRS%20components%20mounted%20on%20the%20top%20surface%20of%20the%20wing%20%20(NTSB%20Photo)-Master.PDF - Photo 6 - Red emergency BRS activation handle (NTSB Photo) (item 12, .PDF, 456 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383304&FileExtension=.PDF&FileName=Photo%206%20-%20Red%20emergency%20BRS%20activation%20handle%20%20(NTSB%20Photo)-Master.PDF - Miscellaneous - BRS Ballistic Parachutes: Information for Emergency Personnel (item 13, .PDF, 24 photos, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383271&FileExtension=.PDF&FileName=Miscellaneous%20-%20BRS%20Ballistic%20Parachutes%3A%20%20Information%20for%20Emergency%20Personnel-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 14, .PDF, 146 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40383268&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.