Diamond Aircraft Ind INC DA 20-C1 accident near Beaver Falls, Pennsylvania, March 23, 2012
On March 23, 2012 at about 4:20 pm local time, a Diamond Aircraft Ind INC DA 20-C1, registered N166SE, was substantially damaged in an accident during approach (VFR pattern final) near Beaver Falls, Pennsylvania (Beaver County Airport). It was an instructional flight under general aviation rules (Part 91). 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The operator’s maintenance personnel’s improper adjustment of the engine's fuel system, which resulted in a total loss of engine power.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 23, 2012 · about 4:20 pm local time · cases in 2012
- Place
- Beaver Falls, Pennsylvania · Beaver County Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was seriously injured and 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Diamond Aircraft Ind INC DA 20-C1
- Registration
- N166SE · no longer on the register · serial C0266
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the flight instructor, while on final approach, he perceived that the airplane was low on the desired glidepath. He said that he issued corrective instructions to the student twice before taking the flight controls. The instructor moved the throttle forward to increase power, and the engine stopped producing power. He selected a forced landing site, issued a Mayday call to the tower, and attempted an engine restart. However, he had to conduct a power-off landing on a roadway. Before ground contact, the airplane struck wires, and, during the accident sequence, the nose gear and tail section of the airplane separated. During the examination of the wreckage, the engine was started, and it ran continuously on the airframe using the airplane's own fuel system. However, when the power was reduced to idle, the engine did not respond as expected to subsequent throttle and mixture inputs. After the initial run, the operator's director of maintenance was asked to produce the tools and documents used to calibrate the fuel system at installation. He produced instructions and gauges that resembled those used at the manufacturer’s factory, but no calibration stickers were displayed on the gauges. The gauges were installed, and, during a subsequent engine run, both the metered and unmetered fuel pressure readings were below factory specifications. The fuel system was removed and flow tested at the engine manufacturer's facility. The fuel pump and fuel control assembly were intact, and bench testing demonstrated their ability to function, but both were found with several parameters outside of their respective calibrated specifications. The fuel manifold and nozzles were also tested and found to exhibit a normal flow vs. pressure indication on the test bench. The fuel pump was found adjusted "down" and flowed less than the required fuel flow specifications. The throttle body and mixture control unit were found adjusted to a position that allowed more than the required fuel flow at three specific settings. The combination of both the fuel pump and throttle body mixture control adjustments resulted in an idle fuel flow rate 2.5 times the maximum required. When the throttle was advanced quickly to full throttle, the fuel flow rate was 40 percent of the required rate. This significant transition in fuel flow rates likely resulted in a momentary "cavitation" of the fuel pump, which allowed air to enter the system and resulted in a total loss of engine power.
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
- Loss of engine power (total) during approach (VFR pattern final) defining event
- Off-field or emergency landing during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Personnel issues › Task performance › Maintenance › Scheduled/routine maintenance › Maintenance personnel
- cause Aircraft › Aircraft systems › Fuel system › Fuel distribution › Incorrect service/maintenance other cases naming the fuel system
Flight instructor
- Certificate: flight instructor, commercial pilot
- Ratings: single-engine land; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 550 hours in all; 206 in this make and model; 112 in the last 90 days; 60 in the last 30 days; 466 as pilot in command; 247 on instruments
- Last flight review: February 23, 2011
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: rgt
- Injury: minor injuries
Dual student
- Certificate: student
- Flight time: 30 hours in all; 30 in this make and model; 9 in the last 90 days; 3 in the last 30 days
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 1,756 hours
- Last inspection: annual inspection, December 6, 2011; 69 hours since
- Maximum gross weight: 1,764 lb
- Seats: 2
- Landing gear: fixed
- Engine: Cont Motor IO-240 SER (piston); 0 hours total
- Operator: O Toole Aviation LLC
The flight
- Departed from: BVI Beaver Falls PA at 3:30 pm
- Destination: BVI Beaver Falls PA
- Flight plan: none
- Runway 10, 4,501 ft by 100 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 110° at 4 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 77°F (25°C), dew point 46°F (8°C)
- Altimeter: 30.04 inHg
- Observation at 4:15 pm from BVI, 2 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
6 documents, released by the NTSB on March 21, 2013. 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, 11 pages | View Download |
| 2 | CFI Statement | PDF, 2 pages | View Download |
| 3 | Field Notes - Diamond Aircraft | PDF, 3 pages | View Download |
| 4 | Excerpts of Maintenance Records | PDF, 1 page | View Download |
| 5 | Memorandum for Record: FAA Statement | PDF, 1 page | View Download |
| 6 | Fuel System Inspection | PDF, 4 pages | 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
- N166SE: not on the register today · the record of its deregistration
- Engine: Cont Motor IO-240 SER 111 aircraft carry this series today · as the NTSB recorded it
- Beaver County · nearest airport
- Accidents and incidents in Pennsylvania 1,836 since 1982 · 234 in the last ten years
- Pennsylvania 6,195 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA12LA246.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.
