Cessna 172P accident near Owasso, Oklahoma, July 4, 1996
On July 4, 1996 at about 5:15 pm local time, a Cessna 172P, registered N62511, was substantially damaged in an accident near Owasso, Oklahoma (Gundys 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
Inadequate maintenance by maintenance personnel resulting in inoperative brake system during an aborted takeoff. A factor was the downhill runway condition.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 4, 1996 · about 5:15 pm local time
- Place
- Owasso, Oklahoma · Gundys · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172P · all 172Ps on the register
- Registration
- N62511 · registry record · serial 17275289
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
In order to check the aircraft performance, the pilot decided not to fly the airplane until after conducting a 'highspeed taxi test.' During the test, the speed reached 40 knots and the pilot pulled the power to idle and applied the brakes. The brakes failed with 1,600 feet (the final 700 feet downgrade) of runway remaining and the airplane rolled beyond the departure end of the runway. Examination of the brake system by a mechanic, who had not performed previous work on the airplane, revealed the brake discs were worn beyond approved limits, and areas of the brake pads were worn down to the rivet heads. The wheel bearing grease was hard and all the bearings were dry and pitted. The right side brake cylinder was pitted and leaking. Dirt filled the brake master cylinders. The last annual inspection was completed on 6/10/96, and the airplane was returned to service by a mechanic with a FAA Inspection Authorization.
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: 822 hours in all; 17 in this make and model; 27 in the last 90 days; 19 in the last 30 days
- Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
- Seat: left
The aircraft
- Last inspection: annual inspection, June 10, 1996; 15 hours since
- Maximum gross weight: 2,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-D2J (piston); 0 hours total
The flight
- Flight plan: none
- Runway 17L, 2,620 ft by 30 ft
Weather at the time
- Light: daylight
- Wind: from 135° at 8 knots
- Visibility: 10 statute miles
- Sky: not recorded; scat at 5,000 ft
- Temperature: 90°F (32°C), dew point 0°F (-18°C)
- Altimeter: 30.00 inHg
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 N62511 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.