The U.S. aircraft register, updated daily
Accidents · NTSB WPR17LA114 · Final report

Amateur-built VELOCITY SUV accident near Puyallup, Washington, May 30, 2017

On May 30, 2017 at about 11:00 pm local time, a 2012 amateur-built VELOCITY SUV, registered N399DG, was substantially damaged in an accident during landing (landing roll) near Puyallup, Washington (Pierce County - Thun 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 airplane builder's failure to install safety wires on the brake disc attachment bolts, and the mechanic’s failure to identify the omission during the condition inspection. The subsequent brake disc separation resulted in a loss of directional control during the landing roll.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 30, 2017 · about 11:00 pm local time · cases in 2017
Place
Puyallup, Washington · Pierce County - Thun Field · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built VELOCITY SUV NO SERIES, built 2012
Registration
N399DG · registry record · serial 115
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The private pilot stated that, during the landing roll, the right brake of the experimental amateur-built airplane failed. The airplane subsequently departed the runway and impacted an airport fence, resulting in substantial damage. The airplane was equipped with a castering nosewheel and steering was accomplished through differential brake pressure; therefore, the pilot did not have any other means to either stop the airplane or maintain directional control once it had slowed to a speed below which rudder authority was available. Postaccident examination revealed that the right brake disc had detached from the wheel hub. None of its attachment bolts were found, and the attachment bolts on the left brake disc were loose. The bolts and discs had holes to accommodate safety wires, but no safety wires were found on either assembly. The pilot had recently purchased the airplane following the completion of a condition inspection. Before the inspection, the airplane's builder had adjusted the landing gear, which necessitated removal of the brake discs. The builder could not recall using safety wires to secure the brake discs during the reinstallation, and the mechanic who performed the subsequent inspection also could not recall if safety wires were used.

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

  1. Sys/Comp malf/fail (non-power) during landing (landing roll) defining event
  2. Runway excursion during landing (landing roll)
  3. Collision during takeoff/land during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Aircraft systems › Landing gear system › Brake › Incorrect service/maintenance other cases naming the landing gear
  • cause Aircraft › Aircraft systems › Landing gear system › Brake › Inadequate inspection other cases naming the landing gear
  • cause Personnel issues › Task performance › Maintenance › Scheduled/routine maintenance › Maintenance personnel
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Attain/maintain not possible

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 465.1 hours in all; 25 in this make and model; 65 in the last 90 days; 27 in the last 30 days; 431 as pilot in command
  • Last flight review: August 14, 2016
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 138 hours
  • Last inspection: condition inspection, May 26, 2017; 21 hours since
  • Maximum gross weight: 2,250 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming LIO-360-C1E6 (piston); 0 hours total

The flight

  • Departed from: PLU Puyallup WA at 11:55 pm
  • Destination: PLU Puyallup WA
  • Flight plan: none
  • Runway 35, 3,650 ft by 60 ft

Weather at the time

  • Light: daylight
  • Wind: from 240° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 59°F (15°C), dew point 52°F (11°C)
  • Altimeter: 29.98 inHg
  • Observation at 11:55 pm from KPLU

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on July 28, 2017. 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.

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

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR17LA114.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.