Piper PA-28R-180 accident near Roanoke, Texas, September 22, 2012
On September 22, 2012 at about 6:30 pm local time, a Piper PA-28R-180, registered N4567J, was substantially damaged in an accident during takeoff near Roanoke, Texas (Northwest Regional airport). It was an instructional flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The loss of engine power during takeoff due to fuel contamination. Contributing to the accident was maintenance personnel's failure to adequately correct the water contamination effects. Contributing to the severity of the occupants' injuries was the lack of shoulder restraints.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 22, 2012 · about 6:30 pm local time · cases in 2012
- Place
- Roanoke, Texas · Northwest Regional · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28R-180 · all PA-28R-180s on the register
- Registration
- N4567J · no longer on the register · serial 28R-30430
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot, who had purchased the airplane about 2 months earlier, and the flight instructor departed on an instructional flight. Two witnesses reported that the airplane's engine did not sound right during the takeoff and the ground roll was longer than normal. Just beyond the runway, the airplane turned slightly left and then impacted the top of several trees. Both wings separated and remained lodged in the treetops; first responders noted fuel running from the wings. The emergency locater transmitter (ELT) was in found in the off position. Examination of the engine revealed water and contaminants in the fuel system, especially in the injection servo and fuel pump, which would have resulted in the rough-running engine and loss of engine power. A review of the airplane's maintenance records did not reveal any entries since the pilot had purchased the airplane. The airplane's last maintenance entry was at the annual inspection, which was about the time the airplane was purchased. The entry stated "found water in tanks - sumped tanks, cleaned flow divider, fuel screens and lines." The log also had the entry that stated "c/w FAR 91.207 ELT insp by installing new batteries, due March 2017." The airport manager had witnessed the same pilot depart in the accident airplane about a month earlier; however, the airplane's engine did not sound right, and the pilot returned to the airport. A review of the pilot's logbook revealed an entry "aborted X-country, lost engine power, so landed" on that date. About 2 weeks later, an e-mail from the pilot to family members stated that a clogged fuel injection system was found after the aborted flight. Two days after that, the pilot's logbook reflected 1.1 flight hours with a note that stated "test flight, perfect." On that same date, the pilot wrote a check to a maintenance company at the airport on which the airplane's registration number and "Maint" were written in the memo field. It is likely that either at the annual inspection and/or 2 weeks before the accident, maintenance personnel did not appropriately address the fuel contamination issues that persisted at the time of the accident. The airplane was not equipped with shoulder belts. During the impact sequence, the pilot likely rotated about his lap belt, braced himself with his arms and fractured his shoulders, but his head struck the instrument panel, resulting in his fatal skull injury. The flight instructor similarly rotated forward about his lap belt; his chest and abdomen struck the instrument panel resulting in his fatal injuries. Had the airplane been equipped with single or double shoulder restraints, the pilots' injuries likely would have been less severe and they might have survived.
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
- Fuel contamination during takeoff defining event
- Collision during takeoff/land during takeoff
The NTSB's findings
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid condition other cases naming the fuel system
- factor Aircraft › Aircraft systems › Fuel system › (general) › Not serviced/maintained other cases naming the fuel system
- factor Personnel issues › Task performance › Maintenance › (general) › Maintenance personnel
- factor Aircraft › Aircraft systems › Equipment/furnishings › Flight compartment equipment › Not installed/available other cases naming the cabin, seats and restraints
- factor Aircraft › Aircraft systems › Equipment/furnishings › Passenger compartment equip › Not installed/available other cases naming the cabin, seats and restraints
- Aircraft › Aircraft systems › Equipment/furnishings › Emergency locator beacon › Not used/operated other cases naming the cabin, seats and restraints
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land; instrument: airplane
- Flight time: 477 hours in all; 20 in this make and model
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: fatal
Flight instructor
- Certificate: airline transport pilot, flight instructor, commercial pilot, flight engineer
- Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 9,000 hours in all; 999 in this make and model
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: rgt
- Injury: fatal
The aircraft
- Airframe total time: 7,048 hours
- Last inspection: annual inspection, July 10, 2012
- Seats: 4
- Landing gear: retractable
- Engine: Lycoming IO-360 SER (piston); 0 hours total
The flight
- Departed from: 52F Roanoke TX at 6:30 pm
- Destination: 52F Roanoke TX
- Flight plan: not recorded
- Runway 17, 3,500 ft by 40 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 91°F (33°C), dew point 46°F (8°C)
- Altimeter: 30.05 inHg
- Observation at 6:53 pm from KAFW, 6 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
21 documents, released by the NTSB on December 4, 2014. 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
- N4567J: 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 IO-360 SER 8,560 aircraft carry this series today · as the NTSB recorded it
- Aero Valley Airport · nearest airport
- Accidents and incidents in Texas 6,244 since 1982 · 1,061 in the last ten years
- Texas 29,985 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN12FA654.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.
