# NTSB ERA20CA203: Beech 36, N15DN, Batavia, NY, June 1, 2020 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 4 · Data collection · Final report - Date: June 1, 2020, 12:30 local (16:30 UTC) - Place: Batavia, NY - Coordinates: 43.031665, -78.173332 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=43.0317&lon=-78.1733&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Landing gear not configured](https://openairdocs.org/ntsb-events/095) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed - Report: Approved by Office Director - Investigation class: Class 4 - Basic report with no Prelim publish - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 101370 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA20CA203 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/101370/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=101370 - Page: https://openairdocs.org/ntsb/ERA20CA203 ## Probable cause The pilot's failure to extend the landing gear during a precautionary landing after an electrical failure. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: forgotten action/omission](https://openairdocs.org/ntsb-findings/02041035): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Beech A36, 7 cases](https://openairdocs.org/ntsb-findings/02041035/cases.md?model=1151604), [All aircraft, 440 cases](https://openairdocs.org/ntsb-findings/02041035/cases.md) - [Landing gear system](https://openairdocs.org/ntsb-findings/01023200): Aircraft › Aircraft systems · Not used/operated (probable cause); cases with it: [Beech A36, 2 cases](https://openairdocs.org/ntsb-findings/01023200/cases.md?model=1151604), [All aircraft, 113 cases](https://openairdocs.org/ntsb-findings/01023200/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Electrical system malf/failure](https://openairdocs.org/ntsb-events/332); cases with it: [Beech A36, 2 cases](https://openairdocs.org/ntsb-events/332/sequence.md?model=1151604), [All aircraft, 182 cases](https://openairdocs.org/ntsb-events/332/sequence.md) - [Landing: Landing gear not configured](https://openairdocs.org/ntsb-events/095) (defining event); cases with it: [Beech A36, 14 cases](https://openairdocs.org/ntsb-events/095/sequence.md?model=1151604), [All aircraft, 584 cases](https://openairdocs.org/ntsb-events/095/sequence.md) ## Analysis According to the pilot, after a normal start and runup, he departed the airport and climbed to the cruise altitude. After reaching that altitude, he noted a flashing message indicator on the GPS that stated there was an electrical system issue. The pilot informed air traffic control that he would return to the departure airport to repair the issue, and about 7 miles from the airport, the GPS and primary flight display began to flash. The pilot pulled the circuit breakers to the flashing displays and set up for a straight in approach to the runway. He realized the airplane needed to lose altitude and attempted to extend the flaps, however, the flaps did not extend. He reset the circuit breakers, but the flaps still did not extend. He continued the approach, mistakenly forgot to extend the landing gear, and landed on the runway with the landing gear retracted. During the accident sequence, the fuselage was substantially damaged. After the accident, the pilot realized that he was interrupted during his starting checklist and concluded that he did not turn on the alternators (alternator and standby alternator) during the start procedures. Therefore, the airplane avionics were running on battery power the entire flight, which resulted in a loss of electrical power. He reported no other mechanical malfunctions of the airplane that would have precluded normal operation prior to the accident. ## Factual narrative According to the pilot, after a normal start and runup, he departed the airport and climbed to the cruise altitude. After reaching that altitude, he noted a flashing message indicator on the GPS that stated there was an electrical system issue. The pilot informed air traffic control that he would return to the departure airport to repair the issue, and about 7 miles from the airport, the GPS and primary flight display began to flash. The pilot pulled the circuit breakers to the flashing displays and set up for a straight in approach to the runway. He realized the airplane needed to lose altitude and attempted to extend the flaps, however, the flaps did not extend. He reset the circuit breakers, but the flaps still did not extend. He continued the approach, mistakenly forgot to extend the landing gear, and landed on the runway with the landing gear retracted. During the accident sequence, the fuselage was substantially damaged. After the accident, the pilot realized that he was interrupted during his starting checklist and concluded that he did not turn on the alternators (alternator and standby alternator) during the start procedures. Therefore, the airplane avionics were running on battery power the entire flight, which resulted in a loss of electrical power. He reported no other mechanical malfunctions of the airplane that would have precluded normal operation prior to the accident. ## Aircraft - Registration: [N15DN](https://openairdocs.org/aircraft/N15DN), registered now, S/N E-2472, built 1989 (OpenAirDocs) - Reported make and model: Beech 36 (A36) - Registry model: [Beech A36](https://openairdocs.org/model/beech-a36) (registry code 1151604) (OpenAirDocs) - Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: E-2472 - Year built: 1989 - Airframe hours: 3182.5 - Engines: Continental IO-550 300 horsepower reciprocating - Damage: Substantial damage - Flight: Positioning, Part 91 - Operator: Snowflake Aircraft Llc - Registered owner: Snowflake Aircraft Llc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 7, 2019 - Departed: GVQ, Batavia, NY - Destination: GVQ, Batavia, NY - Airport: GVQ, Genesee County, runway 28, 5,499 × 100 ft, asphalt - Equipment: Onboard weather, Stall warning system, ADS-B, Electronic flight bag or handheld device, Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 57; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review February 15, 2020; seat: left; flight hours: 952 total, 89 in this make and model, 888 as pilot in command, 54 in the last 90 days, 23 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 300° at 11 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 61 °F, dew point 36 °F - Altimeter: 30.21 inHg - Observed at: GVQ ## 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 20200601001939A](https://openairdocs.org/incident/20200601001939A), Jun 1, 2020: Beech A36, Batavia, NY, Substantial damage. On 6/1/2020, N15DN sustained substantial damage in a gear up landing at gvq (Batavia, NY). The pilot picked up the aircraft after maintenance and departed gvq… ## Docket (4 files) The files NTSB released with the investigation on June 26, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=101370. 5.6 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40484879&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Pilot Statements and Interview Summary (item 2, .PDF, 390 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40484880&FileExtension=.PDF&FileName=Pilot%20Statements%20and%20Interview%20Summary-Master.PDF - FAA Statement (item 3, .PDF, 11 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40484881&FileExtension=.PDF&FileName=FAA%20Statement-Master.PDF - Investigative Photographs (item 4, .PDF, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40484882&FileExtension=.PDF&FileName=Investigative%20Photographs-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.