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

Cessna 182 accident near Robstown, Texas, December 30, 2019

On December 30, 2019, a 1963 Cessna 182, registered N3473U, was substantially damaged in an accident during standing (engine(s) start-up) near Robstown, Texas (Nueces County Airport). 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 failure to set the friction lock on the throttle before hand propping the engine, which allowed the airplane to move forward and impact a credit card machine. Contributing to the accident was the malfunction of the parking brake for reasons that could not be determined.

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

What the record shows

Date
December 30, 2019 · cases in 2019
Place
Robstown, Texas · Nueces County Airport · 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
Cessna 182 F, built 1963 · all 182s on the register
Registration
N3473U · no longer on the register · serial 18254873
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that he parked the airplane in front of the fuel pump and refueled both wing tanks before pushing the airplane back. The pilot reported that, while checking to see if the battery would charge before continuing the flight, the propeller turned slowly, and the engine did not start, so he chose to hand prop the airplane. He set the throttle, mixture, and parking brake, and after several attempts, the engine started. The engine appeared to be at idle, but then the rpms increased. The airplane moved forward and impacted the fuel station's credit card machine before he could enter and stop the airplane. The airplane sustained substantial damage to the airframe's bottom firewall area. Examination of the airplane by a Federal Aviation Administration inspector revealed that the throttle's friction lock was working. A check of the parking brake revealed that, even after the parking brake was applied, the airplane moved, and the brake did not function as intended. The reason for the parking brake malfunction was not determined. The accident is consistent with the pilot not setting the friction lock on the throttle and not verifying if the airplane would move when the parking brake was set.

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. Ground handling event during standing (engine(s) start-up)
  2. Loss of control on ground during standing (engine(s) start-up) defining event
  3. Ground collision during standing (engine(s) start-up)

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Lack of action › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › (general) › (general) › Not attained/maintained
  • cause Environmental issues › Physical environment › Object/animal/substance › (general) › Effect on operation
  • factor Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: commercial pilot, private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,055 hours in all; 41.7 in this make and model; 101.3 in the last 90 days; 58 in the last 30 days; 1,055 as pilot in command
  • Last flight review: September 14, 2019
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: none
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,474 hours
  • Last inspection: annual inspection, July 26, 2019
  • Landing gear: fixed
  • Engine: Continental O-470 R (piston); 2,055 hours total

The flight

  • Departed from: KHRL Harlingen TX at 10:20 pm
  • Destination: 1TE4 Marion TX
  • Flight plan: VFR

Weather at the time

  • Light: dusk
  • Wind: from 350° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 68°F (20°C), dew point 46°F (8°C)
  • Altimeter: 29.89 inHg

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 2 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

3 documents, released by the NTSB on January 21, 2020. 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.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
2 Memo PDF, 1 page View Download
3 Photos PDF, 2 pages · our copy View Download

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/CEN20CA047.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.