Norman QUAD CITY CHALLENGER accident near Monroe, Washington, March 13, 2014
On March 13, 2014 at about 2:15 am local time, a 2000 Norman QUAD CITY CHALLENGER, registered N345MN, was substantially damaged in an accident during initial climb near Monroe, Washington (Firstair Field). It was a personal 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 inadequate construction of the propeller bracket, which resulted in its failure during the initial climb and the propeller subsequently departing the airplane.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 13, 2014 · about 2:15 am local time
- Place
- Monroe, Washington · Firstair Field · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Norman QUAD CITY CHALLENGER II, built 2000
- Registration
- N345MN · registry record · serial CH2 1191 CWIDIO
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot, who was also the builder of the experimental pusher-configured airplane, stated that he made a normal departure from his base airport. As the airplane reached about 250 feet above ground level (agl) he transitioned from the best-angle of climb configuration to the best-rate of climb configuration. The airplane emitted a loud "bang" behind the pilot and the engine subsequently experienced a total loss of power. He established a shallow turn back toward the airport and landed in a field just south and adjacent to the runway. The airplane touched down in soft, wet grass and the right main landing gear collapsed. The fuselage was substantially damaged. After egressing the airplane, the pilot noted that the propeller had separated from the airplane. Upon closer examination, he discovered that the metal bracket he had constructed to support the propeller as part of the speed reduction system had fractured. He estimated that the bracket had amassed about 10 hours of flight time on it.
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
- Aircraft maintenance event during prior to flight
- Flight control sys malf/fail during initial climb defining event
The NTSB's findings
- cause Personnel issues › Task performance › Maintenance › Fabrication › Owner/builder
- cause Aircraft › Aircraft propeller/rotor › Propeller system › Propeller assembly › Incorrect service/maintenance
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 167 hours in all; 33 in this make and model; 74 as pilot in command
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: frt
- Injury: no injuries
The aircraft
- Last inspection: condition inspection, July 9, 2013
- Landing gear: fixed
- Engine: Rotax 503 (piston); 33 hours total
The flight
- Departed from: W16 Monroe WA at 1:00 am
- Destination: W16 Monroe WA
- Flight plan: none
- Runway 25, 2,087 ft by 34 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
- Altimeter: 30.19 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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.