Amateur-built MURPHY MOOSE accident near Marysville, Washington, August 15, 2019
On August 15, 2019 at about 1:53 am local time, a 2019 amateur-built MURPHY MOOSE, registered N525SG, was destroyed in an accident during approach near Marysville, Washington (Arlington Municipal Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain terrain clearance while turning to final approach to avoid a collision with another airplane flying a straight in approach to the same runway. Contributing to the accident was the pilots of both airplanes failure to adequately monitor the airport environment.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 15, 2019 · about 1:53 am local time
- Place
- Marysville, Washington · Arlington Municipal Airport · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built MURPHY MOOSE, built 2019
- Registration
- N525SG · no longer on the register · serial 300
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
A witness at the pilot’s departure airport reported that the airplane’s take off appeared normal but that he saw black smoke emitting from the engine exhaust. Several witnesses in the vicinity of the accident site reported seeing the airplane flying at a low altitude and banking left before it descended nose down to the ground. One of these witnesses stated that the airplane appeared to be “out of control,” and another one of these witnesses reported that the airplane was descending “at a dangerous speed.” Other witnesses reported hearing the engine “pop,” “overrevving,” and “missing or puttering.” Two witnesses reported seeing another airplane near the accident airplane. One witness reported that the other airplane was slightly ahead of and above the accident airplane and that the airplanes were “unusually close.” The other witness reported that he saw the accident airplane banking left and it looked like it was going to cut off another airplane. The accident airplane then “plunged toward the ground.” A review of radar data, GPS, and engine monitoring data revealed that the airplane departed the airport to the north at full engine power before it turned left near the destination airport. About 3 minutes into the flight, the engine rpm fluctuated between 2,260 and 2,900 rpm for 3 minutes before it returned to full power. Concurrently, another airplane, which could not be identified because both airplanes were being operated under visual flight rules and squawking “1200,” was approaching the airport from the south to what appeared to be a straight in approach to the same runway. When the accident airplane was southwest of the destination airport, it started to turn north to final approach toward the destination runway while descending about 1,000 ft per minute (fpm) at full power. The unidentified airplane continued flying north directly toward the same runway. About 1.2 nautical miles south of the runway, the accident airplane was west and slightly north of the unidentified airplane. At their closest point, the two airplanes were within 0.22 mile of each other, and both were about 500 ft above ground level. The engine remained at full power and the airplane’s descent rate had increased to 4,000 fpm 7 seconds before the recorded data ended. The unidentified airplane continued north, flew over the runway, made a left teardrop turn over the airport, then departed the area toward the south. The destination airport does not have an air traffic control tower, and the common traffic advisory frequency is not recorded; therefore, the investigation could not determine if either pilot was communicating over the radio. The accident pilot had recently built the airplane, and the accident flight was its second flight. The airplane’s first flight was about 1 month before the accident. After landing at the destination airport, the pilot refueled the airplane, and it experienced an unspecified electrical problem. The pilot then flew back to the departure airport. During landing, the airplane touched down hard and exited the runway. A witness reported that the engine did not sound like it was running “well” during high-speed taxi tests the day before the accident. Examination of the airframe and engine revealed no preaccident mechanical malfunctions or failures that would have precluded normal operation and the engine monitoring data indicated that the engine was at full power. It could not be determined if the pilot’s attention was distracted by an unknown issue encountered inflight. It is likely that the pilots in both airplanes were not communicating over the common airport traffic frequency or adequately monitoring traffic in the airport environment. The accident pilot likely descended the airplane during a left turn to avoid a collision with the other airplane and did not have sufficient altitude to clear terrain.
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 control in flight during approach defining event
- Collision with terrain or object (not controlled flight into terrain) during approach
The NTSB's findings
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
- Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 375 hours in all; 1 in this make and model
- Medical certificate: None
- Seat: unk
- Injury: fatal
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 4,000 lb
- Seats: 4
- Landing gear: fixed
- Engine: Vedeneyev M14-PF (piston); 0 hours total
The flight
- Departed from: WN53 Lake Stevens WA at 1:43 am
- Destination: AWO Arlington WA
- Flight plan: none
- Runway 34, 5,332 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 310° at 11 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 57°F (14°C)
- Altimeter: 30.13 inHg
- Observation at 1:56 am from AWO, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
11 documents, released by the NTSB on February 1, 2022. 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 | Cockpit Displays A�� Recorded Flight Data - Specialist's Factual Report | PDF, 7 pages | View Download |
| 2 | Cockpit Displays A�� Recorded Flight Data - Attachment 1 (Csv Data) | data file | Download |
| 3 | Air Traffic Control | PDF, 6 pages | View Download |
| 4 | Air Traffic Control - Attachment 1 - FAA radar Data | GZ file | Download |
| 5 | Record of Conversation - Pilot/witness | PDF, 1 page | View Download |
| 6 | Witness Statements - Courtesy of the Marysville Police Department | PDF, 2 pages | View Download |
| 7 | GPS Flight Track on Google Earth | map file | Download |
| 8 | On Scene Observations | PDF, 12 pages | View Download |
| 9 | Record of Memorandum - Autopsy | PDF, 1 page | View Download |
| 10 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
| 11 | Toxicological Report | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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.
