Cessna 172P accident near Concord, North Carolina, March 9, 2003
On March 9, 2003 at about 1:15 am local time, a Cessna 172P, registered N52546, was substantially damaged in an accident near Concord, North Carolina (Concord Regional 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 improper flare during touchdown and failure to properly recover from a bounced landing, which resulted in a loss of control and inflight collision with the runway. A factor was the pilot did not understand the porpoise condition during landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 9, 2003 · about 1:15 am local time
- Place
- Concord, North Carolina · Concord Regional · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172P · all 172Ps on the register
- Registration
- N52546 · registry record · serial 17274552
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot initiated the landing flare at idle or very low power, and the airplane bounced about four times. Each bounce was higher and more pronounced than the previous one. The pilot stated that he thought the bounces would stop, and he concentrated on keeping the airplane as straight as possible on the runway. After the third or fourth bounce, the nosewheel tire blew, and the propeller struck the ground. The airplane came to a stop in the center of the runway, and the pilot shut down the engine. The pilot stated that, after the accident, he flew with a flight instructor and learned what a porpoise condition is, how to recognize it, and how to recover the airplane from it.
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
- Flight time: 145 hours in all; 143 in this make and model; 6 in the last 90 days; 2 in the last 30 days; 67 as pilot in command
- Last flight review: February 18, 2002
- Medical certificate: Class 2 (valid medical--w/ waivers/lim.)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 9,298 hours
- Last inspection: 100-hour inspection, January 16, 2003; 54 hours since
- Maximum gross weight: 2,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-D2J (piston); 0 hours total
The flight
- Departed from: JQF Concord NC
- Destination: JQF Concord NC
- Flight plan: VFR
- Runway 20, 5,500 ft by 100 ft
Weather at the time
- Light: night
- Wind: from 200° at 8 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 59°F (15°C), dew point 43°F (6°C)
- Altimeter: 30.07 inHg
- Observation at 1:15 am from KJQF
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 1 |
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.
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.