SEA07CA159 · Nelson Murphy SR3500 Moose
Nelson Murphy SR3500 Moose · Accident: airframe, component or system failure during landing
From Anacortes Airport (74S) to Roche Harbor Airport (WA09)
Event
- NTSB case
- SEA07CA159
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Nelson Murphy SR3500 Moose
- Aircraft type
- Nelson MURPHY SR3500 MOOSE
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N623AM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Anacortes Airport (74S), Anacortes, WATo Roche Harbor Airport (WA09), Roche Harbor, WA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Landing gear, normal brake system › Jammed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said he was landing on runway 07 with a 5-knot right crosswind. He said that shortly after touchdown, the aircraft started a slight drift to the right. The pilot said he applied left rudder to compensate and felt a "thunk" as the left rudder pedal locked forward, over center, underneath the brake pedal, which prevented the use of the left brake. The aircraft briefly lurched to the left. He applied hard right rudder, but with no apparent effect. He next applied right brake and intentionally ground looped the aircraft to prevent going down an embankment on the south side of the runway. The airplane's left main landing gear collapsed, followed by the left wing, left aileron, and forward fuselage being wrinkled and bent. The pilot said that the rudder/brake pedal assembly has only one master cylinder for the braking system and it is located on the right hand side. He said there is a mechanical linkage from the right to the left, which is prone to jamming in certain rudder pedal deflections. He said that other pilot's have reported this problem with their amateur-built airplanes manufactured from the same kit.
Probable cause
The jamming of the left brake during landing. A factor was the kit manufacturer's design of the brake system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07CA159
- Event ID
- 20070723X00991
- Case number
- SEA07CA159
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-06-15.
- API snapshot SHA-256: 106e643697f82d0ad0d85dfbfa1fc34a0d1d0e1d8be616188ed8a73a3ea08e77; retrieved 2026-09-21T08:48:04.725Z.