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

Cessna 172R accident near New Braunfels, Texas, October 11, 2007

On October 11, 2007 at about 4:30 pm local time, a Cessna 172R, registered N24547, was substantially damaged in an accident near New Braunfels, Texas (New Braunfels Municipal airport). It was an instructional 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 improper recovery from a bounced landing.

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

What the record shows

Date
October 11, 2007 · about 4:30 pm local time · cases in 2007
Place
New Braunfels, Texas · New Braunfels 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
Cessna 172R · all 172Rs on the register
Registration
N24547 · registry record · serial 17280796
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The 35-hour solo student pilot landed hard, bounced, and lost control of the airplane while landing. The mishap occurred during the student's fifth solo landing of the day. The pilot added that after the airplane bounced, the airplane assumed a nose-high attitude, and he overcorrected by pushing the nose over which developed into a porpoise. The airplane porpoised about 4 times before settling into a normal landing roll. The pilot reported the incident to his instructor after he taxied back to the ramp. Examination of the airplane revealed structural damage to the engine firewall. The winds at the time of the mishap were reported as calm.

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: student
  • Flight time: 35 hours in all; 35 in this make and model; 25 in the last 90 days; 11 in the last 30 days; 3 as pilot in command
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,532 hours
  • Last inspection: 100-hour inspection, August 1, 2007
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-lL2A (piston); 0 hours total

The flight

  • Departed from: New Braunfels TX at 11:00 am
  • Destination: New Braunfels TX
  • Flight plan: none
  • Runway 35, 5,364 ft by 100 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 81°F (27°C), dew point 64°F (18°C)
  • Altimeter: 29.96 inHg
  • Observation at 3:55 pm from KBAZ

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.

Connections how this case links to the rest of the register

Aircraft
Place

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