- Date
- October 9, 2005, 10:42 local (14:42 UTC)
- Place
- Lakeland, FL
- Injuries
- 1 serious, 2 minor
- Damage
- Destroyed
- Phase of flight
- Initial climb
- Aircraft
- N6413SBeech 95-B55
- Weather
- Visual (VMC) · Day
- Status
- Completed · report November 29, 2006
- Report
- Approved by Office Director
- Parties
- FAA Flight Standards District Office, Teledyne Continental Motors
- FAA report
- 20051009026659A
- Case key
- 62631
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The failure of the pilot-in-command to abort the takeoff.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
Before takeoff the main fuel tanks were filled; postaccident testing of a specimen of fuel from the truck that fueled the accident airplane revealed the sample met specification for 100 Low Lead fuel. An engine run-up before takeoff was performed by the pilot-rated passenger in the left front seat and the rpm decrease when checking each magneto was approximately 75. The flight was cleared to takeoff from runway 27 with all runway available (8,500 feet), and the pilot reported the airplane became airborne in no more than 2,000 feet. The Pilot's Operating Handbook and FAA Approved Airplane Flight Manual (POH/AFM) indicates that based on the conditions at the time of the accident, the total distance to clear a 50-foot obstacle was 2,250 feet. The pilot reportedly climbed at blue-line airspeed and kept the landing gear retracted until insufficient runway remained to land where he was flying at 50 feet above ground level. The POH/AFM indicates that the airplane was capable of climbing at 800 feet-per-minute with the landing gear and flaps extended, and full power on both engines. The controller reported that the airplane was climbing "very slow", and he did not hear of a loss of engine power nor did he see smoke trailing from the engines during takeoff. The pilot reported that when he retracted the landing gear, the engine sound decreased and he sensed the airplane was not accelerating, but this was not indicated on the engine gauges, nor was it indicated by the airplane yawing,so he did not check for an engine out. He confirmed the throttle, mixture, and propeller controls were full forward, and a short time later he heard the stall warning horn and pitched down to maintain blue-line airspeed. He thought about returning to the departure airport but lost altitude during a turn. He lowered the landing gear, flew under powerlines, and impacted in a field in a wings level attitude. All occupants exited the airplane which was destroyed by the postcrash fire. Examination of the engines following recovery revealed no evidence of preimpact failure or malfunction. Postcrash fire damage to the engine accessories and controls precluded bench or operational testing.
Factual narrative
On October 9, 2005, about 1042 eastern daylight time, a Beech 95-B55, N6413S, registered to Master Craft Plumbing, Inc., was landed in a field shortly after takeoff from Lakeland Linder Regional Airport (KLAL), Lakeland, Florida. Visual meteorological conditions prevailed at the time and an instrument flight rules (IFR) flight plan was filed for the 14 CFR Part 91 personal flight from Lakeland Linder Regional Airport, to Page Field Airport, Fort Myers, Florida. The airplane was destroyed by a postcrash fire and the commercial-rated pilot, and private-rated passenger sustained minor injuries, while one passenger seated in one of the two rear seats sustained serious injuries. The flight originated about 1 minute earlier from Lakeland Linder Regional Airport.
The pilot-in-command (PIC) seated in the right seat stated that the flight had landed earlier that day following an uneventful 30-minute flight, and after landing, both main fuel tanks were filled. Before takeoff he personally checked the fuel level in the left tank and noted it was full. The left seat occupant checked the fuel level in the right tank. He (PIC) "...then walked around the aircraft inspecting it. Everything appeared normal." The airplane was taxied to runway 27 (8,500 foot long runway), where an engine run-up was performed by the pilot-rated passenger, who was in the left seat. When performing a check of each magneto the engine rpm decrease for each was approximately 75. During the takeoff roll, the airplane became airborne in no more than 2,000 feet, and he climbed maintaining blue-line airspeed. When the airplane was near the end of the runway while flying at 50 feet above ground level (agl), with insufficient runway remaining to land, he placed the landing gear selector handle to the up position to retract the landing gear. At that time, he heard the engine sound decrease and sensed the airplane was not accelerating. The engine gauges did not indicate a loss of power and the airplane did not yaw in any direction, so he "...did not try to check for a engine-out." He confirmed the throttle, mixture, and propeller controls were full forward, and a few seconds later he heard the stall warning horn which he silenced by pitching the airplane down to maintain blue-line airspeed. While maintaining altitude flying at blue-line airspeed at 100 feet, he thought about returning to the airport, but committed himself to an off airport landing. He saw a field that was approximately 70 degrees to the flight path of the airplane, descended to 50 feet agl, and lowered the landing gear selector handle. He banked to the right to land in the field, flew under powerlines, and impacted the ground in a wings level attitude. A postcrash fire occurred and all occupants exited the airplane after it came to rest.
The pilot-rated left front seat occupant stated that after landing following the 30-40 minute flight, he put in a request to "...top off both tanks." While in a restaurant on the airport, he observed a truck with markings "AvGas" and "Truck 1" pulling up to fuel the airplane. He verbally reported taking a sample of fuel from only 1 sump drain under each wing and noted the samples smelled like 100 low lead (100LL) fuel, and both had a blue tint; no discrepancies were reported. He further reported that he started the engines and the engine run-up before takeoff was "normal." They were advised by the tower controller to position and hold and the pilot-in-command taxied onto the runway over the "27 marking." They received their IFR clearance and the PIC "...did our normal takeoff procedure which, in the Baron, is to advance the throttles to 2200 rpm while holding the brakes and check the engine gauges. All appeared normal." The PIC released the brakes and applied full power and he (pilot-rated left front seat occupant), perceived everything to be normal. The airplane accelerated past red-line, and the rotation and initial climb felt normal as the PIC retracted the landing gear. He then reported that when the flight was at 250 to 350 feet mean sea level (msl), he noticed they were no longer climbing and he had the sensation of reduced power but he did not notice a yawing motion and the PIC did not appear to have any problem maintaining directional control. A decision was made to continue straight ahead and look for a place to land since they lost altitude while banking. A north/south oriented road was noted and the PIC maneuvered the airplane to land on the road. The airplane flew under powerlines then landed and bounced around a few times. Flames were immediately seen and the PIC opened the cabin entry door and exited the airplane, and he (pilot-rated left front seat occupant) pulled the right front seat forward so the rear seat occupant could exit the airplane. The pilot-rated left front seat passenger then exited the airplane.
The rear seat passenger stated that he did not detect any engine malfunction during the engine run-up before takeoff. He also reported the acceleration and the initial climb after takeoff were normal but he then felt a "...deceleration as if you were down shifting in a car." The pilot-rated left front seat occupant asked the PIC if he felt that and stated that "...something [happened]." The engines were "...still running fine but now we were barely holding altitude." The tower was advised of the situation and the flight was cleared to return to the airport. A "...bad engine was not identified they both were still running for the moment." The pilot-rated left front seat occupant looked at either the vertical speed indicator or altimeter and verbalized out loud they were descending. The pilot-rated left front seat occupant advised the tower controller that they were going to land off airport and the controller advised they would call fire rescue. The PIC descended below power lines and the airplane impacted the ground flat but he was thrown to the left. Flames occurred on impact in front and behind the right wing, and the PIC had trouble opening the cabin door. He (rear seat passenger), "...dove over the seat and exited the right wing into a wall of flames. I closed my eyes and did not know how far it was to the ground. I fell face down in the field that was on fire. I rolled twice and got up getting away from the wreckage."
According to the controller who cleared the flight to takeoff, the airplane had full length of runway 27 available. He estimated the takeoff roll was approximately 3,000 feet, and after becoming airborne the climb out was "very slow." He commented to a co-worker in the tower that it was not right. While airborne he did not detect a loss of engine power and did not see any yaw, or smoke trailing the engines. He first noticed the landing gear was retracted before the airplane reached the departure end of the runway, and the airplane flew over the departure end of the runway on runway centerline at approximately 100 feet. The airplane then slowly banked to the right heading 300 degrees, and he called Crash/Fire before losing sight of the airplane. He lost sight of the airplane then observed smoke. A helicopter that had previously landed flew to the area and after flying to the area reported the airplane was already on fire. He further reported that since he was only working the accident airplane at the time, he normally can hear if engine(s) are misfiring, and he did not hear any misfiring from the engine(s) of the accident airplane.
During recovery of the airplane, both engines were placed inside the heat damaged fuselage. Examination of the engines following recovery was performed by a representative of the engine manufacturer with FAA oversight.
Examination of the left engine revealed extensive heat damage to the engine, engine accessories, and controls which precluded bench or operational testing of the components and controls. The crankshaft was fractured aft of the propeller flange; t
Aircraft
- Registration
- N6413S
- Reported as
- Beech 95-B55
- Category
- Airplane
- Serial number
- TC-1923
- Airframe hours
- 2,633.1
- Engine
- Continental IO-470-L, 260 horsepower, reciprocating
- Damage
- Destroyed
- Fire
- On-Ground
- Flight
- Personal · Part 91
- Registered owner
- Master Craft Plumbing, Inc.
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · June 1, 2005
- Departed
- KLAL · Lakeland, FL
- Destination
- KFMY · Fort Myers, FL
- Flight plan
- IFR
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 24
- Injuries
- Minor
- Certificates
- Flight instructor, Commercial
- Airplane ratings
- Multi-engine land, Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 1, Without waivers/limitations
- Seat
- Right
- Flight hours
- 750 total · 60 in this make and model · 680 as pilot in command · 150 in the last 90 days · 50 in the last 30 days · 3 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 280° at 4 knots
- Visibility
- 12 statute miles
- Lowest ceiling
- 1,300 ft broken
- Temperature
- 82 °F, dew point 73 °F
- Altimeter
- 29.78 inHg
- Observed at
- KLAL
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N6413S · 1
Matched to the same aircraft by N-number and date.