# NTSB NYC03LA146: Cessna 172N, N314TM, Linden, NJ, July 2, 2003 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: July 2, 2003, 12:15 local (16:15 UTC) - Place: Linden, NJ - Coordinates: 40.617221, -74.244445 - Nearby events: https://openairdocs.org/map.md?lat=40.6172&lon=-74.2444&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report April 28, 2004 - Report: Approved by Office Director - Parties: Textron Lycoming Engines, FAA/FSDO, Cessna Aircraft Company - NTSB case key (mKey): 57368 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC03LA146 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/57368/pdf - Page: https://openairdocs.org/ntsb/NYC03LA146 ## Probable cause The mechanic's improper installation of the carburetor, and his failure to secure the mixture control wire to the mixture control arm pivot bolt. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power, takeoff - initial climb - maintenance,installation - improper, other maintenance personnel (cause) - mixture control,linkage - not secured (cause) - Forced landing, emergency descent/landing - In flight collision with object, emergency landing - object - other ## Analysis The purpose of the flight was to ferry the airplane to a maintenance facility to have the carburetor examined. During the takeoff climb, about 300 feet above the ground, the engine began to "run rough" for about 10 seconds, then lost total power. The pilot performed a forced landing to the only grass area in the vicinity, and during the landing, the airplane impacted a gas pipeline. Examination of the engine revealed that the mixture control wire was not secured to the mixture control arm pivot bolt. A review of the maintenance records revealed the carburetor was replaced five days prior to the accident, with the entry stating, "..set idle speed and mixture to specs." ## Factual narrative On July 2, 2003, at 1215 eastern daylight time, a Cessna 172N, N314TM, was substantially damaged during a forced landing after takeoff from Linden Airport (LDJ), Linden, New Jersey. The certificated commercial pilot received minor injuries. Visual meteorological conditions prevailed for the personal flight which was destined for the Princeton Airport (39N), Princeton, New Jersey. No flight plan was filed for the flight which was conducted under 14 CFR Part 91. The accident pilot was also the maintenance officer for the flying club that operated the airplane. He stated that the carburetor had been replaced on the airplane the week prior to the accident, and the airplane had experienced several abnormal events since its installation. The purpose of the accident flight was to fly to Princeton to have the carburetor re-examined. According to the pilot, he performed a run up inspection prior to his departure and noticed no anomalies. The takeoff roll and liftoff were also "normal," and he again noticed no anomalies. About 300 feet above the ground, the engine began to "run rough" for about 10 seconds, then lost total power. The pilot performed a forced landing to the only grass area in the vicinity, and during the landing, the airplane impacted a gas pipeline. The engine was examined under the supervision of a Federal Aviation Administration inspector. Examination of the engine revealed that the mixture control wire was not secured to the mixture control arm pivot bolt. The engine was rotated by hand at the propeller flange, and compression and valve train continuity were obtained on all cylinders with the exception of the number 3 cylinder, which exhibited impact damage. The carburetor was disassembled and examined, with no mechanical anomalies noted. A review of the maintenance records revealed the carburetor was replaced on June 27, 2003, with the entry stating, "..set idle speed and mixture to specs." ## Aircraft - Registration: [N314TM](https://openairdocs.org/deregistered/N314TM-2013-12-30), registration cancelled 2013-12-30, S/N 17270052, built 1977 (OpenAirDocs) - Reported make and model: Cessna 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17270052 - Airframe hours: 6080 - Engines: Lycoming O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Positioning, Part 91 - Registered owner: Richmond Pilots Association - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 4, 2002, 197 hours before - Departed: LDJ, Linden, NJ - Destination: 39N, Princeton, NJ - Airport: LDJ, Linden Airport, runway 27, 4,137 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; injuries: none; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; last flight review August 3, 2001; seat: left; flight hours: 2,200 total, 1,600 in this make and model, 2,100 as pilot in command, 50 in the last 90 days, 15 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 170° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: 25,000 ft overcast - Temperature: 82 °F, dew point 59 °F - Altimeter: 29.98 inHg - Observed at: EWR, 6 nm away ## 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 20030702030429A](https://openairdocs.org/incident/20030702030429A), Jul 2, 2003: Cessna 172N, Linden, NJ, Destroyed. (-23) Engine was not running properly during takeoff. Pilot continued the take off and the engine failed at approximately 300 ft AGL. Pilot made off airport… 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.