Beech C17B accident near Stevensville, Maryland, June 14, 2009
On June 14, 2009 at about 5:27 pm local time, a Beech C17B, registered N47024, was substantially damaged in an accident during landing (landing roll) near Stevensville, Maryland (Bay Bridge Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain directional control of the airplane 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
- June 14, 2009 · about 5:27 pm local time · cases in 2009
- Place
- Stevensville, Maryland · Bay Bridge Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech C17B · all C17Bs on the register
- Registration
- N47024 · registry record · serial C17B-102
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that after takeoff in the tailwheel-equipped airplane the flight proceeded to the destination airport and the automated weather observing station (AWOS) indicated the wind was favoring runway 29. The flight continued and while on final approach to runway 29, the AWOS indicated the wind was from 360 degrees at 7 knots; no gusts were reported. The airplane landed on the main landing gear, and within seconds of lowering the tailwheel, the airplane suddenly veered to the right. The pilot applied right aileron, left rudder, and left brake to stop the turn but was unsuccessful. The airplane departed the runway and collided with a ditch. The spars of the lower left wing were damaged. Inspection of the airplane following recovery by a FAA certificated airframe and powerplant mechanic with inspection authorization (A&P/IA) revealed no evidence of preimpact failure or malfunction of the tailwheel assembly.
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
- Loss of control on ground during landing (landing roll) defining event
- Runway excursion during landing (landing roll)
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
- Flight time: 9,171 hours in all; 1,148 in this make and model; 67 in the last 90 days; 25 in the last 30 days; 8,921 as pilot in command; 4,371 on instruments
- Last flight review: July 28, 2008
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,437 hours
- Last inspection: annual inspection, April 20, 2009
- Maximum gross weight: 3,165 lb
- Seats: 5
- Landing gear: retractable
- Engine: Jacobs L4 /R755-7 (piston); 0 hours total
The flight
- Departed from: PJC Zelienople PA at 3:15 pm
- Destination: W29 Stevensville MD
- Flight plan: IFR
- Runway 29, 2,903 ft by 60 ft
Weather at the time
- Light: daylight
- Wind: from 350° at 4 knots
- Visibility: 10 statute miles
- Sky: scat at 4,000 ft
- Temperature: 77°F (25°C), dew point 64°F (18°C)
- Altimeter: 29.98 inHg
- Observation at 5:50 pm from ESN, 16 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on August 25, 2009. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Weather Reports and Records | PDF, 1 page | View Download |
| 3 | Record of NTSB Conversation | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N47024 the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N47024 on the register today · the tail number may have moved to another aircraft since
- Beechcraft C17 11 registered today · the model family and its accident history
- Beechcraft 6 aircraft on the register
- Engine: Jacobs L4 /R755-7 225 aircraft carry this series today · as the NTSB recorded it
- Bay Bridge Airport · nearest airport
- Zelienople Municipal · departed from
- Accidents and incidents in Maryland 837 since 1982 · 111 in the last ten years
- Maryland 2,356 aircraft registered
- Other NTSB records under N47024 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/ERA09CA350.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.