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

Cessna 172 accident near Baltimore, Maryland, March 24, 2017

On March 24, 2017 at about 2:30 pm local time, a 1973 Cessna 172, registered N13499, was substantially damaged in an accident during taxi near Baltimore, Maryland (Martin State Airport). It was an instructional 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 student pilot’s failure to maintain clearance from other airplanes in the run-up area.

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

What the record shows

Date
March 24, 2017 · about 2:30 pm local time
Place
Baltimore, Maryland · Martin State Airport · map
Type
Accident · collision on the ground
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 M, built 1973 · all 172s on the register
Registration
N13499 · no longer on the register · serial 17262796
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The solo student pilot reported that, as she taxied into the run-up area, the right wing impacted a parked airplane. The airplane continued and then impacted two other airplanes in the run-up area. The airplane sustained substantial damage to both wings. The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

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 collision during taxi defining event

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring environment › Student/instructed pilot
  • cause Environmental issues › Physical environment › Object/animal/substance › Aircraft › Effect on operation

Dual student

  • Certificate: student
  • Flight time: 43.5 hours in all; 43.5 in this make and model; 14.6 in the last 90 days; 4.4 in the last 30 days; 9.1 as pilot in command
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,927.9 hours
  • Last inspection: 100-hour inspection, February 10, 2017
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-A4M (piston); 1,039 hours total
  • Operator: Middle River Aviation LLC

The flight

  • Departed from: MTN Baltimore MD at 2:45 pm
  • Destination: MTN Baltimore MD
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 190° at 10 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 9,000 ft
  • Temperature: 46°F (8°C), dew point 30°F (-1°C)
  • Altimeter: 30.44 inHg
  • Observation at 2:55 pm from KMTN

Injuries

FatalSeriousMinorNone
Flight crew1

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

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

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.