Beech C24R accident near Valparaiso, Florida, June 23, 2011
On June 23, 2011 at about 9:44 am local time, a Beech C24R, registered N38029, was substantially damaged in an accident during maneuvering near Valparaiso, Florida (Eglin Air Force Base airport). It was an instructional flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilots’ failure to maintain airspeed, which resulted in an inadvertent, low altitude aerodynamic stall.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 23, 2011 · about 9:44 am local time
- Place
- Valparaiso, Florida · Eglin Air Force Base · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech C24R · all C24Rs on the register
- Registration
- N38029 · no longer on the register · serial MC-746
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During a night instructional flight, the private pilot under instruction attempted a 360-degree power off approach. The maneuver, which is also practiced as a simulated engine failure, involves a 360-degree change of direction to a preselected landing spot. The pattern is designed to be circular, but the turn may be shallowed, steepened, or discontinued at any point to adjust the accuracy of the flight path. Flaps and landing gear can also be used to control descent rate. The maneuver generally commences about 2,000 feet over the intended landing spot (high key), descends to a 180-degree position about 1,000 to 1,200 feet (downwind key, or low key), continues to a 90-degree position about 800 feet (base-leg key) with a turn to final at a minimum of 300 feet. Radar data revealed that the airplane commenced the maneuver about 2,000 feet over the runway, but arrived at a 180-degree position about 400 feet high, and at a 90-degree position about 500 feet high. It continued around the circuit still high, and approaching the runway, the flight instructor advised the controller that student training was in progress, right base for the “option.” After being cleared for the option, the airplane descended to 1,100 feet over the runway. It then began a right turn away from the runway and had descended to 900 feet when the instructor stated that they were doing another 360-degree circuit. There were no further transmissions from the airplane, but there were two more radar returns, one at 900 feet, and the last at 600 feet in the right turn. About that time, a number of witnesses heard the engine “sputter,” but then all witnesses subsequently heard the engine power up. They then saw the airplane descend at a steep angle and impact an aircraft parking apron, coming to a stop in about 600 feet. Because of a postcrash fire, not all engine items could be extensively examined. Those that could, did not reveal any engine anomalies, except that one fuel injector was found completely blocked, while another was partially blocked, most likely due to thermal effects from the fire. Propeller ground scars indicated power at the time of ground impact. The engine had over 2,380 hours of operation since its last overhaul, and another pilot reported that he had an engine failure while overflying an outlying airport about 12 months earlier, which maintenance personnel could not duplicate. During that failure, the engine did not sputter, and it could not be restarted, either in flight or on the ground until the following day. No subsequent engine operating anomalies were noted. Radar and wreckage path evidence indicated the likelihood that neither pilot adequately monitored the airplane’s airspeed, which resulted in a right-turning aerodynamic stall. One pilot then attempted a recovery by adding power; however, by the time he did so, there was insufficient altitude to avoid the ground. The reason for the pilots’ distraction from monitoring airspeed cannot be definitively determined; whether related to the power-off approach, the sputtering engine, or something altogether different. However, in all scenarios, it remained incumbent upon both pilots to ensure that proper airspeed was maintained, which they did not do.
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
What happened, in order
- Simulated/training event during approach
- Loss of control in flight during maneuvering defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
- Fire/smoke (post-impact) during post (impact)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Personnel issues › Psychological › Attention/monitoring › Monitoring equip/instruments › Pilot
- cause Personnel issues › Psychological › Attention/monitoring › Monitoring equip/instruments › Instructor/check pilot
Flight instructor
- Certificate: flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 17,453 hours in all; 334 in this make and model; 158 in the last 90 days; 72 in the last 30 days; 13,490 on instruments
- Last flight review: January 18, 2010
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: rgt
- Injury: fatal
Dual student
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 472 hours in all; 44 in this make and model; 79 in the last 90 days; 47 in the last 30 days; 429 as pilot in command
- Last flight review: December 28, 2010
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 9,253 hours
- Last inspection: 100-hour inspection, April 23, 2011; 49 hours since
- Maximum gross weight: 2,750 lb
- Seats: 4
- Landing gear: retractable
- Engine: Lycoming IO-360SER A&C (piston); 0 hours total
- Fire on the ground
- Operator: Eglin Air Force Base Aero Club
The flight
- Departed from: VPS Valparaiso FL at 7:21 pm
- Destination: VPS Valparaiso FL
- Runway 01, 1,012 ft by 300 ft
- A second pilot was aboard
Weather at the time
- Light: night, dark
- Wind: from 280° at 3 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 1,900 ft; scat at 1,600 ft
- Temperature: 79°F (26°C), dew point 73°F (23°C)
- Altimeter: 29.95 inHg
- Observation at 9:55 am from VPS
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
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.
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA11FA354.
