SEA07CA032 · Riley D-16A
Riley D-16A · Accident: airframe, component or system failure during takeoff
From Point Roberts Airpark (1RL) to Point Roberts Airpark (1RL)
Event
- NTSB case
- SEA07CA032
- 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
Riley D-16A
- Aircraft type
- Riley D-16
- 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
- N119N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Point Roberts Airpark (1RL), Point Roberts, WATo Point Roberts Airpark (1RL)
- 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
- Takeoff · roll/run
- 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, nose gear › Cracked
- Landing gear, wheel › Separation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, during the takeoff roll at about rotation speed, he felt the nose landing gear of the airplane "give way" and the airplane began to drift to the left. As he applied right rudder to correct the yaw, he felt "a continued collapse" of the nose landing gear and elected to abort the takeoff. The airplane's nose and both propellers struck the ground. Examination of photos provided by an insurance adjustor revealed that both engines were displaced down and to the right. The right engine firewall was torn from the engine nacelle, and the left engine firewall was buckled and distorted. Additionally, the photos revealed that the nose landing gear fork had broken into two pieces, which allowed the nose wheel to separate from the airplane, resulting in collapse of the nose landing gear. The pilot reported that "an aircraft structural engineer made the observation that my nose gear fork had an old hidden crack that could have contributed to the failure."
Probable cause
the pre-existing crack in the nose wheel fork, which allowed separation of the nose wheel during the takeoff roll, resulting in collapse of the nose landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07CA032
- Event ID
- 20070119X00074
- Case number
- SEA07CA032
- 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: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 5dccbb9fbb7d493ab37e4efe27572052ef1d0f08374cbea693535b1f1dcd01cd; retrieved 2026-09-22T04:11:37.661Z.