Cessna 172M accident near Fresno, California, July 10, 1999
On July 10, 1999 at about 3:00 pm local time, a Cessna 172M, registered N73113, was substantially damaged in an accident near Fresno, California (Sierra Sky Park 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 misjudged landing flare and inadequate recovery procedures from the subsequent bounced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 10, 1999 · about 3:00 pm local time
- Place
- Fresno, California · Sierra Sky Park · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172M · all 172Ms on the register
- Registration
- N73113 · registry record · serial 17267269
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot flew over the airport and determined the winds were light. On final approach he set the flaps to 30 degrees and maintained 68 to 70 knots. About 1/8 mile from the runway, he reduced power to idle. He began his flare over the runway numbers and noted the airplane continued to float over the runway. He gently raised the nose and heard the stall warning horn; however, the airplane continued to float. The airplane dropped onto the main landing gear, bounced into the air, came down on the nose gear, and bounced into the air again. The pilot was aware that the nose tire had blown so he added power, kept the control yoke back, and settled onto the runway. He then taxied to a parking spot. A mechanic replaced the nose tire and cleared the airplane for flight. The pilot departed and returned to Fresno. Subsequent inspection revealed the firewall was wrinkled.
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: 85 hours in all; 16 in this make and model; 16 in the last 90 days; 3 in the last 30 days; 17 as pilot in command
- Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
- Seat: left
The aircraft
- Airframe total time: 4,354 hours
- Last inspection: 100-hour inspection, July 7, 1999; 5 hours since
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-E2D (piston); 0 hours total
The flight
- Departed from: FAT CA at 2:45 pm
- Destination: Q60
- Flight plan: none
- Runway 30, 2,920 ft by 50 ft
Weather at the time
- Light: daylight
- Wind: at 3 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 22,000 ft; clear
- Temperature: 82°F (28°C), dew point 52°F (11°C)
- Altimeter: 30.00 inHg
- Observation at 2:56 pm from FAT, 9 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 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.
Other NTSB records under N73113 the same tail number, which may have belonged to a different aircraft at the time
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.
