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

Cessna 172R accident near Louisburg, North Carolina, May 28, 2005

On May 28, 2005 at about 1:10 pm local time, a Cessna 172R, registered N22055, was substantially damaged in an accident near Louisburg, North Carolina (Franklin 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 maintain adequate airspeed, which resulted in a stall and subsequent loss of control and collision with the ground.

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

What the record shows

Date
May 28, 2005 · about 1:10 pm local time
Place
Louisburg, North Carolina · Franklin County · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172R · all 172Rs on the register
Registration
N22055 · registry record · serial 17280902
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot was attempting a simulated engine-out landing and initiated a go-around. He stated he applied full power, and the left wing dropped. He stated he countered with control input, then the right wing dropped. He countered with control input, and the left wing dropped again and made contact with the ground. He stated the airplane then contacted the runway in a "nose slightly down attitude." Examination of the airplane revealed the propeller was damaged, the nosewheel was separated, the right main wheel was separated, both wings were bent, and the fuselage was buckled aft of the baggage door. No mechanical malfunction of the airplane was reported or observed.

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

Pilot

  • Certificate: private
  • Ratings: single-engine land; single-engine sea
  • Flight time: 325 hours in all; 325 in this make and model; 3 in the last 90 days; 1 in the last 30 days; 257 as pilot in command
  • Last flight review: March 18, 2004
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: 100-hour inspection
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 0 hours total
  • Operator: First In Flight Aviation

The flight

  • Departed from: KLHZ Louisburg NC at 8:40 am
  • Destination: KLHZ Louisburg NC
  • Flight plan: none
  • Runway 22, 5,500 ft by 100 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Crew1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Other NTSB records under N22055 the same tail number, which may have belonged to a different aircraft at the time

1984-02-12MKC84LA072 · accident near Conway Springs, KS · substantial damage · no injuries

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.