Aircraft in Troy Gentry helicopter crash identified as Schweizer 269
The helicopter that crashed in New Jersey in 2017, killing Troy Gentry of Montgomery Gentry, has been identified as a Schweizer 269 C-1, according to official records.
2 reports on this incident · first at Sep 8, 2026, 4:33 p.m. ET
Earlier reports
Sep 8, 2026, 4:33 p.m. ETFirst report
Troy Gentry of Montgomery Gentry Dies in Helicopter Crash in New Jersey
Troy Gentry, half of the country duo Montgomery Gentry, died in a helicopter crash on September 8, 2017, in Medford, New Jersey, according to americansongwriter.com. The crash occurred before a scheduled performance at the Flying W Airport & Resort. The helicopter was piloted by James Evan Robinson. Engine problems brought the helicopter down in a wooded area, the outlet reported. The pilot died instantly; Gentry died hours later at a hospital. The duo had just finished recording their album 'Here's to You' days before the crash.
The aircraft, a Schweizer 269 helicopter, was registered as N204HF, according to the official NTSB accident record (case ERA17FA317). Registry records list it as a Schweizer 269 C-1 single-engine piston helicopter. The cause of the crash has not been determined.
The NTSB database lists one other case involving the Schweizer 269 C-1 since 2008, which involved a fatality. This record says nothing about the cause of this accident.
Was this report accurate and useful?
Reference data
From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.
- Registration
- N204HF
- Type
- Schweizer 269 C-1 — single-engine piston helicopter
- Terrain elevation
- 69 ft
- Nearest aerodrome
- 2.5 miles SSW of Flying W Airport (KN14)
Sources
Revision history
- Version 18 Sept 2026, 20:37current
First published.
- Version 18 Sept 2026, 20:33current
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.