# NTSB CEN14LA345: Cessna 210L, N1175Q, Las Vegas, NM, July 3, 2014 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: July 2, 2014, 18:30 local (Jul 3, 2014, 00:30 UTC) - Place: Las Vegas, NM - Coordinates: 35.654167, -105.142501 - Nearby events: https://openairdocs.org/map.md?lat=35.6542&lon=-105.1425&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Serious injuries - Injuries: 1 serious, 3 minor - Status: Completed, report February 3, 2016 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Continental Motors, FAA - Albuquerque FSDO, Textron Aviation - NTSB case key (mKey): 89623 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN14LA345 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89623/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89623 - Page: https://openairdocs.org/ntsb/CEN14LA345 ## Probable cause The pilot's loss of airplane control during an aborted landing. Contributing to the accident was the pilot's inadequate preflight planning, which resulted in his attempt to land on a runway closed by a notice to airmen and the loss of engine power due to fuel exhaustion. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 210L, 1 case](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=2073448), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 210L, 3 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2073448), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Planning/preparation: flight planning/navigation](https://openairdocs.org/ntsb-findings/02061025): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 210L, 1 case](https://openairdocs.org/ntsb-findings/02061025/cases.md?model=2073448), [All aircraft, 179 cases](https://openairdocs.org/ntsb-findings/02061025/cases.md) - [Planning/preparation: fuel planning](https://openairdocs.org/ntsb-findings/02061030): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 210L, 2 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=2073448), [All aircraft, 719 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md) - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Cessna 210L, 2 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=2073448), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 210L, 4 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2073448), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 210L, 5 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2073448), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The private pilot reported that, when the airplane was about 200 ft above the ground on final approach after a cross-country flight, he saw vehicles and flashers on the runway. He attempted to abort the landing and started climbing the airplane, but the fuel "started cutting out," and he subsequently lost airplane control. A postaccident examination of the airplane, engine, and systems revealed no anomalies. There was no evidence of a fuel spill, and no fuel was visible within the wing fuel tanks. The fuel monitoring instrument indicated that 288 gallons of fuel were used and that 0 gallon of fuel was remaining. The airplane's total fuel capacity was 90 gallons; therefore, it is apparent that the pilot did not reset the fuel monitoring instrument after the airplane was refueled, which resulted in the instrument indicating an inaccurate fuel quantity. It is not known how much fuel was on board the airplane before its departure or whether it would have been sufficient to complete the trip. At the time of the accident, the runway was undergoing construction activities, and a notice to airmen (NOTAM) had been issued to close the runway for a period of about 3 days, including the accident date. Based on the evidence, it is likely that the pilot did not conduct adequate preflight planning, which resulted in his lack of awareness that the runway was closed by a NOTAM and his subsequent attempt to abort the landing. Further, his inadequate preflight planning did not ensure that there was sufficient fuel on board for the flight, which resulted in fuel exhaustion and the subsequent loss of engine power during the aborted landing. ## Factual narrative HISTORY OF FLIGHT On July 2, 2014, about 1830 mountain daylight time (mdt), a Cessna 210L, N1175Q, was substantially damaged during a loss of control during an attempted go-around from runway 14, at the Las Vegas Municipal Airport (LVS), Las Vegas, New Mexico. The pilot received serious injuries and the three passengers received minor injuries. The aircraft was registered to and operated by the private pilot under the provisions of 14 Code of Federal Regulations (CFR) Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, which was not operated on a flight plan. The flight originated from the Ames Municipal Airport (AMW), Ames, Iowa, at an unconfirmed time. The pilot reported to first responders that he was attempting to land on runway 14. He stated that he checked ahead to see if there was any weather or issues with runway 14 but received no response. He proceeded to attempt a landing on runway 14 and when he was about 200 feet above the ground he noticed vehicles and flashers on the runway. He told the first responder that he applied power and started climbing but stated that the "fuel 'started cutting out'" and he lost control. A passenger in the airplane reported to the first responder that she heard her father (the pilot), call the tower to make sure it was ok to land and he received no response. She stated that they then noticed work trucks so he tried to "pull up", but didn't have enough time and the airplane crashed. PERSONNEL INFORMATION According to Federal Aviation Administration records, the pilot held a private pilot certificate with a single engine land airplane rating. The pilot also held a second class medical certificate issued on January 24, 2014. Partial pilot flight logbook records were reviewed. The last entry reviewed indicated that the pilot had accumulated 350.4 hours total flight time. He had received training in the accident airplane, including a high performance checkout, as required by 14 CFR Part 61.31, on July 19, 2013. According to the records, the training lasted 3.2 hours. The records showed that the pilot had accumulated 41.8 hours of experience in the accident airplane as of the last reviewed entry dated August 17, 2013. AIRCRAFT INFORMATION The airplane was a 1972 Cessna 210 L airplane. It was a single-engine, high wing monoplane configured to seat 6 occupants. The airplane had a retractable tricycle landing gear and was constructed predominately from aluminum. The airplane was powered by a 6 cylinder Continental IO-520-L engine rated to produce 300 horsepower. Maintenance records for the airplane showed that the most recent annual inspection as required by 14 CFR Part 91.409, was completed on June 27, 2013. At the time of the inspection the airplane had accumulated 5,729.84 hours total time in service, and the engine had accumulated 1,466.64 hours since overhaul. METEOROLOGICAL INFORMATION At 1853, the recorded weather conditions at LVS were: Wind 150 degrees at 13 knots; 10miles visibility; few clouds at 4,900 feet above ground level; temperature 19 degrees Celsius; dew point 9 degrees Celsius; altimeter setting 30.32 inches of mercury. AIRPORT INFORMATION At the time of the accident, LVS was an uncontrolled airport and did not have an operating control tower. Aircraft operating in the vicinity of LVS used the common traffic advisory frequency (CTAF) to announce their intentions. LVS had two intersecting runways, runway 14/32, and runway 2/20. A notice to airmen (NOTAM) was in effect for runway 14/32 at LVS. The NOTAM stated that runway 14/32 was to be closed from July 1, 2014, at 1100 mdt, to July 3, 2014, at 2000 mdt. There were no other NOTAMs for LVS. WRECKAGE AND IMPACT INFORMATION On site examination of the airplane revealed that the landing gear was in the down position, although the nose landing gear and left main landing gear had collapsed. The fuel selector valve handle was in-between the left position and the off position. There was no evidence of a fuel spill at the accident scene and no fuel was visible in the wing tanks. Further examination of the airplane was conducted subsequent to its removal from the accident site and no anomalies were found with respect to the airframe, engine, or other airplane systems. The airplane was equipped with a JPI instruments EDM-700 engine monitor, and a JPI FS-450 fuel monitor, both of which were retained for further examination. The EDM-700 did not have recording capability. The FS-450 had recording capability limited to fuel used and fuel available. After the accident the instrument indicated 288.1 gallons of fuel used, and 0 gallons of fuel remaining. ADDITIONAL INFORMATION The Cessna 210L was powered by a 300 horsepower Continental IO-520-L engine. It had a fuel capacity of 90 gallons with 89 gallons useable. The straight line distance from AMW to LVS is 658 nautical miles. According to performance charts for the airplane, at 8,000 feet pressure altitude and standard temperature, the airplane could cruise at 171 knots at a fuel burn of 15 gallons per hour. Based on these figures, about 60 gallons of fuel were required for the flight, however, it is not known how much fuel was on-board the airplane prior to the start of the flight. ## Aircraft - Registration: [N1175Q](https://openairdocs.org/deregistered/N1175Q-2018-02-27), registration cancelled 2018-02-27, S/N 21059675, built 1972 (OpenAirDocs) - Reported make and model: CESSNA 210L (M) - Registry model: [Cessna 210L](https://openairdocs.org/model/cessna-210l) (registry code 2073448) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 21059675 - Year built: 1972 - Airframe hours: 5730 - Engines: CONT MOTOR IO 520 -L 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, June 27, 2013 - Departed: AMW, Ames, IA - Destination: LVS, Las Vegas, NM - Airport: LVS, Las Vegas Muni, runway 14, 8,199 × 75 ft, asphalt - Equipment: Stall warning system, Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 50; injuries: serious; private; airplane ratings: single-engine land; medical: class 2, without waivers/limitations; seat: left; flight hours: 350 total, 42 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 150° at 13 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 66 °F, dew point 48 °F - Altimeter: 30.31 inHg - Observed at: LVS ## 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 20140702012579A](https://openairdocs.org/incident/20140702012579A), Jul 2, 2014: Cessna 210L, Las Vegas, NM, Substantial damage. Pilot attempted to land on closed runway 32 at lvs. After seeing men and equipment on the runway, PIC attempted a go-around. Aircraft unable to go-around and… ## Other investigations on N1175Q (1) 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. - [NTSB NYC75FNE27](https://openairdocs.org/ntsb/NYC75FNE27-130698), Jun 5, 1974: Cessna 210 (N1175Q), Meriden, CT, substantial damage ## Docket (9 files) The files NTSB released with the investigation on December 24, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89623. 8.2 MB in all. - Wreckage Examination Notes (item 1, .PDF, 17 photos, 3.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435192&FileExtension=.PDF&FileName=Wreckage%20Examination%20Notes-Master.PDF - Police Report (item 2, .PDF, 431 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435193&FileExtension=.PDF&FileName=Police%20Report-Master.PDF - Electronic Devices Factual Report (item 3, .PDF, 4 photos, 415 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435194&FileExtension=.PDF&FileName=Electronic%20Devices%20Factual%20Report-Master.PDF - NOTAM Information (item 4, .PDF, 45 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435195&FileExtension=.PDF&FileName=NOTAM%20Information-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 5, .PDF, 140 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435197&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Master.PDF - Pilot Flight Record Excerpts (item 6, .PDF, 896 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435198&FileExtension=.PDF&FileName=Pilot%20Flight%20Record%20Excerpts-Master.PDF - Maintenance Record Excerpts (item 7, .PDF, 441 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435199&FileExtension=.PDF&FileName=Maintenance%20Record%20Excerpts-Master.PDF - Evidence Control Form (item 8, .PDF, 174 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435200&FileExtension=.PDF&FileName=Evidence%20Control%20Form-Master.PDF - Photos (Courtesy of Aircraft Recovery Service) (item 9, .PDF, 4 photos, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435196&FileExtension=.PDF&FileName=Photos%20(Courtesy%20of%20Aircraft%20Recovery%20Service)-Master.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.