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

Alon A2 accident near Richmond Hts., Ohio, August 31, 2009

On August 31, 2009 at about 6:50 pm local time, a Alon A2, registered N6363V, was substantially damaged in an accident during landing (flare/touchdown) near Richmond Hts., Ohio (Cuyahoga County 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 control of the airplane during the landing flare.

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

What the record shows

Date
August 31, 2009 · about 6:50 pm local time · cases in 2009
Place
Richmond Hts., Ohio · Cuyahoga County 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
Alon A2 · all A2s on the register
Registration
N6363V · registry record · serial A-39
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported the crosswind landing approach was normal. Just before touching down, the airplane ballooned to an altitude of about 15 feet above the runway. The airplane "mushed hard" onto the runway, then veered off the right side of the runway where it contacted a taxiway light, resulting in substantial damage to the airplane. Local winds were from 340 degrees at 10 knots and the airplane was landing on runway 06.

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. Loss of control in flight during landing (flare/touchdown) defining event
  2. Abnormal runway contact during landing (flare/touchdown)
  3. Runway excursion during landing (flare/touchdown)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 322 hours in all; 200 in this make and model; 12 in the last 90 days
  • Last flight review: April 24, 2008
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Maximum gross weight: 1,450 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Cont Motor C90-16F (piston); 0 hours total

The flight

  • Departed from: 2G2 Steubenville OH at 6:00 pm
  • Destination: CGF Richmond Hts. OH
  • Flight plan: none
  • Runway 06, 5,102 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 340° at 10 knots
  • Visibility: 20 statute miles
  • Sky: scat at 300 ft
  • Temperature: 72°F (22°C), dew point 50°F (10°C)
  • Altimeter: 30.25 inHg
  • Observation at 6:50 pm from CGF

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

1 document, released by the NTSB on September 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.

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