The U.S. aircraft register, updated daily
Accidents · NTSB ERA18LA175 · Final report

Aircraft Mfg & Development CO CH 2000 accident near Newburyport, Massachusetts, June 20, 2018

On June 20, 2018 at about 4:45 pm local time, a 2004 Aircraft Mfg & Development CO CH 2000, registered N239AM, was substantially damaged in an accident during landing near Newburyport, Massachusetts (Plum Island airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 20, 2018 · about 4:45 pm local time · cases in 2018
Place
Newburyport, Massachusetts · Plum Island · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Aircraft Mfg & Development CO CH 2000 UNDESIGNAT, built 2004 · all CH 2000s on the register
Registration
N239AM · no longer on the register · serial 20-1039
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Other weather encounter during approach
  2. Loss of control in flight during approach
  3. Attempted remediation/recovery during approach (VFR go-around)
  4. Collision during takeoff/land during landing defining event
  5. Runway excursion during landing

The NTSB's findings

  • cause Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Response/compensation
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Personnel issues › Action/decision › Action › Delayed action › Pilot
  • cause Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Effect on operation

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 149 hours in all; 22 in this make and model; 31 in the last 90 days; 8 in the last 30 days; 55 as pilot in command
  • Last flight review: October 2, 2017
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Last inspection: annual inspection, April 5, 2018
  • Maximum gross weight: 1,692 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235 (piston); 0 hours total
  • Operator: Bald Eagle Flying Club

The flight

  • Departed from: PWM Portland ME at 3:42 pm
  • Destination: 2B2 Newburyport MA
  • Flight plan: none
  • Runway 28, 2,105 ft by 50 ft

Weather at the time

  • Light: daylight
  • Wind: at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 77°F (25°C), dew point 54°F (12°C)
  • Altimeter: 29.81 inHg
  • Observation at 4:53 pm from BVY, 13 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 6 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

3 documents, released by the NTSB on February 11, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA18LA175.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.