# NTSB ERA18LA175: Aircraft Mfg & Development CH 2000, N239AM, Newburyport, MA, June 20, 2018 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: June 20, 2018, 12:45 local (16:45 UTC) - Place: Newburyport, MA - Coordinates: 42.79639, -70.839447 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=42.7964&lon=-70.8394&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report April 30, 2019 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 97556 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA18LA175 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/97556/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=97556 - Page: https://openairdocs.org/ntsb/ERA18LA175 ## Probable cause The pilot's failure to adequately compensate for existing crosswind conditions during the final approach and landing flare, which led to the airplane drifting left of the runway, and his delayed decision to go around, which resulted in the airplane touching down in the grass next to the runway and a subsequent collision with trees. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Response/compensation (probable cause); cases with it: [Aircraft Mfg & Development CH 2000, 1 case](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=0033001), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Aircraft Mfg & Development CH 2000, 6 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=0033001), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Aircraft Mfg & Development CH 2000, 1 case](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=0033001), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Aircraft Mfg & Development CH 2000, 2 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=0033001), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [Aircraft Mfg & Development CH 2000, 1 case](https://openairdocs.org/ntsb-events/400/sequence.md?model=0033001), [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md) - [Approach: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Aircraft Mfg & Development CH 2000, 3 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=0033001), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Approach-VFR go-around: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Aircraft Mfg & Development CH 2000, 2 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=0033001), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Aircraft Mfg & Development CH 2000, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=0033001), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Aircraft Mfg & Development CH 2000, 2 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=0033001), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The private pilot reported that, after a personal, cross-country flight, he entered the traffic pattern at the destination airport and noted a 20° left crosswind between 9 and 11 knots. The final approach was stable, but after crossing the threshold, the airplane descended and drifted left over grass adjacent to the runway. Because the airplane was not over the runway, the pilot chose to conduct a go-around and added full power, but the left main landing gear struck the grass next to the runway. The airplane did not climb and continued drifting left. The pilot retracted the flaps in an attempt to gain altitude; however, the airplane still did not climb, and the stall warning horn activated. He pushed the yoke forward to avoid a stall, and the airplane touched down on the grass and then impacted trees, which resulted in substantial damage to the wings and fuselage. The pilot reported that there were no mechanical malfunctions or failures with the airplane that contributed to the accident. A stand of trees was located left of the runway. It is possible that the trees blocked the crosswind when the airplane descended below treetop level and that the pilot did not adequately compensate for the existing winds during the final approach and landing flare. ## Factual narrative On June 20, 2018, about 1245 eastern daylight time, Aircraft Manufacturing and Development Company CH2000, N239AM, was substantially damaged during a go-around at Plum Island Airport (2B2), Newburyport, Massachusetts. The private pilot sustained minor injuries. The airplane was operated by Bald Eagle Flying Club under the provisions of 14 Code of Federal Regulations part 91 as a personal flight. Visual meteorological conditions prevailed, and no flight plan was filed for flight that originated at Portland International Airport (PWM), Portland, Maine at 1142 and was destined for 2B2.The pilot reported that he entered at the traffic pattern at 2B2 following an uneventful flight from PWM. The windsock showed a 20° left crosswind between 9 and 11 kts for runway 28. The approach to runway 28 was stable at 65 kts and the airplane was configured properly over the threshold. After crossing the threshold, the airplane descended and drifted to the left. The airplane was no longer over the runway, so the pilot elected to go around. He added full power and the left main gear struck the grass next to the runway. The airplane was not gaining altitude and continued to the left. He retracted the flaps with the hope of gaining altitude; however, the airplane did not climb and the stall warning horn activated. He pushed the yoke forward to avoid a stall and the airplane touched down on the grass and then collided with trees. An inspector with the Federal Aviation Administration responded to the accident site and examined the wreckage. He reported that the airplane came to rest in an area of thick brush and trees. There was no fire. The wings and fuselage sustained structural damage. The nose when was separated and found about 8 ft west of the main wreckage. The propeller and spinner were separated from the engine. An examination of the runway revealed no skid or tire marks that would indicate touchdown on the paved surface. The first indication of touchdown was found in the grass, about ½ way down the 2,105 ft runway and 200 feet left of the runway edge. Several propeller slash marks were found in the ground, 20 ft west of the initial touchdown point. A stand of trees was located south and west of runway 28. The pilot reported 149 hours of total flight time, including 22 hours in the accident airplane make and model. He reported that there were no mechanical malfunctions of failures with the airplane prior to the accident. ## Aircraft - Registration: [N239AM](https://openairdocs.org/deregistered/N239AM-2021-10-30), registration cancelled 2021-10-30, S/N 20-1039, built 2004 (OpenAirDocs) - Reported make and model: AIRCRAFT MFG & DEVELOPMENT CO CH 2000 (UNDESIGNAT) - Registry model: [Aircraft Mfg & Development CH 2000](https://openairdocs.org/model/aircraft-mfg-development-ch-2000) (registry code 0033001) (OpenAirDocs) - Registry engine: [Lycoming 0-235 series](https://openairdocs.org/engine/lycoming-0-235-series) (registry code 41505, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 20-1039 - Year built: 2004 - Engines: Lycoming O-235 117 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Bald Eagle Flying Club - Registered owner: Bald Eagle Flying Club - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 5, 2018 - Departed: PWM, Portland, ME - Destination: 2B2, Newburyport, MA - Airport: 2B2, Plum Island, runway 28, 2,105 × 50 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 48; injuries: minor; private; airplane ratings: single-engine land; medical: class 2, without waivers/limitations; last flight review October 2, 2017; seat: left; restraint: 3-point; flight hours: 149 total, 22 in this make and model, 55 as pilot in command, 31 in the last 90 days, 8 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 77 °F, dew point 54 °F - Altimeter: 29.81 inHg - Observed at: BVY, 13 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 20180620013619A](https://openairdocs.org/incident/20180620013619A), Jun 20, 2018: Aircraft Mfg & Development Co CH 2000, Newburyport, MA, Substantial damage. The event occurred at plum island airport (2B2) in Newburyport, Massachusetts at 1240 pm. The airman departed portland, Maine to plum island. The airman… ## Docket (3 files) The files NTSB released with the investigation on February 11, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=97556. 7.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 5.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470228&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - NTSB Memorandum for Record - FAA Inspector Interview (item 2, .PDF, 61 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470229&FileExtension=.PDF&FileName=NTSB%20Memorandum%20for%20Record%20-%20FAA%20Inspector%20Interview-Master.PDF - Photo Array (item 3, .PDF, 6 photos, 1.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470230&FileExtension=.PDF&FileName=Photo%20Array-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.