ASN Wikibase Occurrence # 34837
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | Friday 12 November 1993 |
Time: | 06:29 |
Type: | Piper PA-31-350 Chieftain |
Owner/operator: | Cherokee Leasing Inc t/a Cherokee Express |
Registration: | N27687 |
MSN: | 31-7852107 |
Year of manufacture: | 1978 |
Total airframe hrs: | 8393 hours |
Fatalities: | Fatalities: 1 / Occupants: 1 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | Barton Boulevard, Orlando, Orange County, FL -
United States of America
|
Phase: | Take off |
Nature: | Cargo |
Departure airport: | Orlando Executive Airport, Orlando, Florida (ORL/KORL) |
Destination airport: | Tampa, Florida (TPA/KTPA) |
Confidence Rating: | Information is only available from news, social media or unofficial sources |
Narrative:On November 12, 1993, about 06:29 EST (Eastern Standard Time), a Piper PA-31-350, N27687, registered to Cherokee Leasing, Inc., operated by Cherokee Express, crashed into a residential area shortly after takeoff from the Orlando Executive Airport, Orlando, Florida. The flight was operating under 14 CFR Part 135 as a nonscheduled, domestic, cargo flight, call sign "Blue Max 500". Visual meteorological conditions prevailed at the time and a VFR flight plan was filed for the flight to Tampa, Florida. The airplane was destroyed by a post-crash fire and the pilot was fatally injured. One house was fire damaged and one of the two occupants received minor injuries. The flight was originating at the time of the accident.
Before takeoff the airplane was loaded with checks and bank documents and the pilot-in-command did not complete the required load manifest nor did she leave a copy with the company as required by the FAA approved company operations manual.
At 06:22.49 CST, "Blue Max 500" was cleared to taxi to runway 7. While taxiing to takeoff, the accident airplane passed in front of another airplane which gave the other pilot an unobstructed view of the left side of the "Blue Max 500" airplane. The pilot stated that he observed "a lot" of black smoke trailing from the exhaust of the left engine. He further stated that the "Blue Max 500" airplane was at the run-up area for about 1-2 minutes, but he couldn't hear whether the pilot had performed an engine run-up of each engine before departure. His attention was diverted and he did not witness the takeoff roll or accident.
At 06:26.28 CST, the pilot of the "Blue Max 500" flight contacted the tower controller and advised that the flight was ready for departure, southwest. At 06:26.35 CST, the tower controller advised the pilot that the flight was cleared for takeoff, which the pilot acknowledged 8 seconds later. At 06:28.53 CST, the pilot of the "Blue Max 500" flight advised the controller "... i i need to come back round and land on uh runway 25 here." At 06:28.58 CST, the controller advised the pilot that the flight was cleared to land on runway 25. There was no further radio contact with the pilot of the "Blue Max 500" flight.
According to one witness who observed the takeoff roll and initial climb, the takeoff roll seemed slower than normal and the pilot seemed to use more runway than normal for this type of airplane. He also stated that he heard popping sounds from the engines during the takeoff roll. He observed the airplane climbing slowly maintaining runway heading but then observed the airplane descending after which the airplane began to bank to the left loosing altitude during the turn. After 180 degrees of turn had been completed the wings were observed to level with respect to the horizon, then the nose of the airplane was observed to pitch down and the airplane banked to the left in about a 90- degree angle of bank. The airplane then descended nose and left wing low until he lost sight of the airplane due to obstructions. He then observed black smoke.
According to numerous other witnesses near the accident site, the airplane was observed flying east-northeast bound after takeoff low and slow and was observed to bank to the left in what one witness described as the right wing was nearly vertical. The airplane then descended through several trees, impacted the ground, and came to rest adjacent to a house. The airplane was destroyed by a post-crash fire and the house was damaged by the fire.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
WAS IN FLIGHT LOSS OF CONTROL FOR FAILURE OF THE PILOT-IN-COMMAND TO MAINTAIN VMC SHORTLY AFTER TAKEOFF. CONTRIBUTING TO THE ACCIDENT WAS PARTIAL LOSS OF ENGINE POWER FROM THE LEFT ENGINE DUE TO PARTIAL BLOCKAGE OF SEVERAL OF THE FUEL INJECTOR NOZZLES. ALSO CONTRIBUTING TO THE ACCIDENT WAS WEIGHT AND BALANCE EXCEEDED BY THE PILOT-IN-COMMAND AND INADEQUATE SURVEILLANCE BY THE COMPANY AND BY THE FAA.
Registration N27687 cancelled by the FAA on May 21, 1996 as "Destroyed"
Sources:
1. NTSB Identification: MIA94FA020 at
https://www.ntsb.gov/_layouts/ntsb.aviation/brief2.aspx?ev_id=20001211X13773&ntsbno=MIA94FA020&akey=1 2. FAA:
http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=27687 3.
http://www.scramble.nl/civil-database/details?bt=pa&af=3211 4. [LINK NOT WORKING ANYMORE:http://www.baaa-acro.com/1993/archives/crash-of-a-piper-pa-31-navajo-chieftain-in-orlando-1-killed/]
5.
http://articles.orlandosentinel.com/1993-11-16/news/9311160126_1_pilot-error-crash-orlando-executive 6.
http://planecrashmap.com/plane/fl/N27687/ Revision history:
Date/time | Contributor | Updates |
24-Oct-2008 10:30 |
ASN archive |
Added |
30-Apr-2015 00:59 |
Dr. John Smith |
Updated [Time, Operator, Location, Nature, Departure airport, Destination airport, Source, Narrative] |
30-Apr-2015 01:05 |
Dr. John Smith |
Updated [Location, Source] |
30-Apr-2015 01:06 |
Dr. John Smith |
Updated [Location] |
11-Oct-2017 00:29 |
Dr. John Smith |
Updated [Location, Source, Narrative] |
20-Nov-2022 08:01 |
Ron Averes |
Updated [Location] |
20-Nov-2022 22:50 |
Ron Averes |
Updated [Location, Narrative] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation