Piper PA-28 accident near Ray, Michigan, May 27, 2017
On May 27, 2017 at about 3:35 pm local time, a 1969 Piper PA-28, registered N5584U, was substantially damaged in an accident during landing (flare/touchdown) near Ray, Michigan (Ray Community Airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain a proper approach speed, which resulted in in a hard landing and a runway excursion. Contributing to the accident was the pilot's decision to fly the airplane without an instructor onboard.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 27, 2017 · about 3:35 pm local time · cases in 2017
- Place
- Ray, Michigan · Ray Community Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28 140, built 1969 · all PA-28s on the register
- Registration
- N5584U · no longer on the register · serial 28-26314
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot (the owner of the airplane) was landing at the airport following a local flight. Witnesses reported that the airplane made several landing attempts, but, each time, the airplane was too fast or too high to land. On the last attempt, the airplane touched down hard and fast about halfway down the 2,495-ft-long runway. The airplane continued off the end of the runway, across a road, through a field, and struck several small trees and a tractor before coming to a stop. An examination of the airplane's systems revealed no pre-impact anomalies that contributed to the accident. A flight instructor who had previously flown with the pilot told the pilot that he should fly only with an instructor on board, and that he was not ready to fly the airplane alone. Thus, it is likely that the pilot did not have the necessary experience to conduct a successful landing in the airplane.
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
- Hard landing during landing (flare/touchdown) defining event
- Loss of control on ground during landing (landing roll)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- factor Personnel issues › Experience/knowledge › Experience/qualifications › Total experience w/ equipment › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 210 hours in all; 50 in this make and model; 150 as pilot in command
- Last flight review: September 10, 2016
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 3,715 hours
- Last inspection: annual inspection, July 1, 2016
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming 0-320 SERIES (piston); 0 hours total
The flight
- Departed from: 57D Ray MI
- Destination: 57D Ray MI
- Flight plan: none
- Runway 9, 2,495 ft by 60 ft
Weather at the time
- Light: daylight
- Wind: from 150° at 5 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 300 ft
- Temperature: 66°F (19°C), dew point 59°F (15°C)
- Altimeter: 29.89 inHg
- Observation at 2:58 pm from KMTC, 8 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 1 picture 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
7 documents, released by the NTSB on October 27, 2017. 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, 9 pages | View Download |
| 2 | Pilot's Statement, Curtis Lynn | PDF, 1 page | View Download |
| 3 | FAA Inspector's Statement | PDF, 2 pages | View Download |
| 4 | Airport Information | PDF, 4 pages | View Download |
| 5 | Weather Information | PDF, 8 pages | View Download |
| 6 | Macomb County, Michigan, Sheriff's Report | PDF, 21 pages | View Download |
| 7 | Photo 1, Accident Airplane | PDF, 1 page · our copy | View Download |
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
- N5584U: not on the register today · the record of its deregistration
- Piper PA-28 Cherokee, Warrior, Archer and Arrow 18,620 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Lycoming 0-320 SERIES 27,304 aircraft carry this series today · as the NTSB recorded it
- Ray Community Airport · nearest airport
- Accidents and incidents in Michigan 2,107 since 1982 · 230 in the last ten years
- Michigan 7,236 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN17LA341.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.

