eFlight
Accidents · NTSB ERA10LA121 · Final report

Luscombe 8A accident near Madison, Georgia, January 19, 2010

On January 19, 2010 at about 4:50 pm local time, a Luscombe 8A, registered N2750K, was substantially damaged in an accident during landing (landing roll) near Madison, Georgia (Madison Municipal 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 maintain directional control while landing with a tailwind.

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

What the record shows

Date
January 19, 2010 · about 4:50 pm local time · cases in 2010
Place
Madison, Georgia · Madison Municipal · 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
Luscombe 8A · all 8As on the register
Registration
N2750K · registry record · serial 5477
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot landed on runway 14 with a tailwind and slowed the airplane to taxi speed in preparation to exit the runway. As the airplane neared the taxiway, it veered sharply to the right. The pilot corrected with left brake and full left rudder. The airplane then veered left and exited the left side of the runway. Upon contact with the unimproved surface, the right main landing gear collapsed and the right wing was damaged. The pilot initially stated that a gust of wind had caused him to ground loop and then later stated that a fractured tailwheel leaf spring had caused a loss of directional control. Metallurgical examination of the fractured leaf spring found no evidence of any preexisting cracking or corrosion, and the fracture surfaces were indicative of overstress. Tire marks observed on the runway were consistent with the main gear and tailwheel tires being in contact with the runway as the airplane departed. Wind reported near the time and location of the accident was from 270 degrees at 7 knots, varying between 247 and 307 degrees.

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 on ground during landing (landing roll) defining event
  2. Runway excursion during landing (landing roll)
  3. Landing gear collapse 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
  • Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Effect on operation

Pilot

  • Certificate: flight instructor, commercial pilot, private
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
  • Flight time: 1,321 hours in all; 250 in this make and model; 3 in the last 90 days; 2 in the last 30 days
  • Last flight review: April 25, 2007
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: annual inspection, July 1, 2009
  • Maximum gross weight: 1,260 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Cont Motor A&C65 SERIES (piston); 0 hours total

The flight

  • Departed from: GA06 Monticello GA at 4:25 pm
  • Destination: 52A Madison GA
  • Flight plan: none
  • Runway 14, 3,806 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 270° at 7 knots
  • Visibility: 9 statute miles
  • Sky: clear
  • Temperature: 61°F (16°C), dew point 45°F (7°C)
  • Altimeter: 30.03 inHg
  • Observation at 5:00 pm from 3J7, 16 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

9 documents, released by the NTSB on September 28, 2010. 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
  • N2750K on the register today · the tail number may have moved to another aircraft since
  • Luscombe 8 Silvaire 1,420 registered today · the model family and its accident history
  • Luscombe 1,472 aircraft on the register
  • Engine: Cont Motor A&C65 SERIES · as the NTSB recorded it
Place

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

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.