Piper PA28 accident near East Moriches, New York, October 20, 2018
On October 20, 2018 at about 4:15 pm local time, a 1982 Piper PA28, registered N8275V, was substantially damaged in an accident during landing near East Moriches, New York (Lufker airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s delayed initiation of a go-around and his subsequent use of the improper go-around procedure, which resulted in a landing area overshoot.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 20, 2018 · about 4:15 pm local time
- Place
- East Moriches, New York · Lufker · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA28 161, built 1982 · all PA28s on the register
- Registration
- N8275V · no longer on the register · serial 28-8316001
- Damage
- Substantial damage
- Flight
- Positioning flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that, during the preflight inspection, he did not observe anything abnormal. He added that, during the initial taxi, the airplane "pulled more power than usual" but that he observed no issues with the brakes or flight controls. The pilot reported that, during approach to a 2,300-ft-long grass airstrip about 60 knots with full flaps, he reduced power to idle to flare. The airplane was "still floating," and about midfield, he saw that the rpm had increased with the power at idle to between about 1,000 to 1,200 rpm. He retracted the flaps to 15° to execute a go-around, but before he increased power, the airplane touched down on the runway. He was going to continue the go-around but realized the airplane would be unable to clear power lines and trees at the end of the runway. He then braked hard but was unable to stop the airplane on the grass, so he shut off the fuel pump and closed the mixture. He added that the "engine did not stop," and the airplane continued moving forward due to momentum. He applied full brakes with an "s turn and 180 turn," the airplane slid on the grass, and the left wing struck a wooden pole. The airplane then came to an abrupt stop. The pilot stated that he saw that the engine and propeller had stopped The airplane sustained substantial damage to the left wing. The Federal Aviation Administration inspector reported that he attempted to examine the engine, but the airplane was unavailable for examination. The airplane manufacturer's prescribed "Go Around" checklist stated: Throttle………………………..FULL Carb Heat……………………….OFF Flaps……….RETRACT TO 20 DEG Vy……………………….….79 KIAS Flaps…………..…RETRACT PROC It is likely that the pilot flew the approach at too high of an airspeed and initiated the go-around too late, which resulted in the airplane floating and the subsequent landing area overshoot.
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
- Abnormal runway contact during landing
- Landing area overshoot during landing defining event
- Attempted remediation/recovery during landing
- Collision with terrain or object (not controlled flight into terrain) during landing
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Delayed action › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › Pilot
- Environmental issues › Physical environment › Object/animal/substance › Pole › Contributed to outcome
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 1,425 hours in all; 252 in this make and model; 200 in the last 90 days; 110 in the last 30 days; 877 as pilot in command
- Last flight review: March 24, 2018
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Last inspection: 100-hour inspection
- Maximum gross weight: 2,326 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320 SERIES (piston); 0 hours total
The flight
- Departed from: FRG Farmingdale NY at 3:00 pm
- Destination: 49N East Moriches NY
- Flight plan: VFR
- Runway S, 2,300 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 260° at 11 knots, gusting 19
- Visibility: 10 statute miles
- Sky: broken clouds at 2,000 ft
- Temperature: 61°F (16°C), dew point 52°F (11°C)
- Altimeter: 29.70 inHg
- Observation at 3:56 pm from KHWV, 5 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 7 pages | View Download |
| 2 | Record of Conversation - Pilot | PDF, 1 page | View Download |
| 3 | Record of Conversation - FAA Inspector | PDF, 1 page | View Download |
| 4 | Accident Photo | PDF, 1 page | View Download |
| 5 | Checklists | PDF, 2 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
