ASN Wikibase Occurrence # 30037
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: | Monday 4 September 2000 |
| Time: | 12:25 |
| Type: |  Beechcraft B95 Travel Air |
| Owner/operator: | Private |
| Registration: | N3WT |
| MSN: | TD409 |
| Total airframe hrs: | 4842 hours |
| Engine model: | Textron Lyc. O-360-A1A |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | 2 miles NW of Tampa Bay Executive Airport, Odessa, Florida -
 United States of America
|
| Phase: | Initial climb |
| Nature: | Private |
| Departure airport: | Odessa, FL (3FD1) |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The accident aircraft was found in a field after an emergency locator transmitter beacon had made an alert of a possible accident having occurred. At about 1225, a witness, who had also been a student pilot, was in a housing development near where the accident aircraft was found, and he said that he had observed an aircraft maneuvering at a low altitude, just above the tree line. He said he saw the aircraft enter a steep bank, and start a dive with its left wing down. According to the witness, the aircraft then went below the tree line, and he waited for signs of an impact, such as noise or smoke, but did not hear or see anything. He said he then assumed that the pilot might have recovered enough to set the aircraft down in the field. He said the aircraft had descended as an eagle would, had it been attacking a small animal. FAA Tampa Approach radar information showed that the accident aircraft had been at 300 feet at 1221:44, and it had climbed to a maximum altitude of 1,100 feet at 1223:35. At 1224:21, radar information showed the aircraft at 700 feet, prior to all radar information being lost. The accident occurred during daylight hours, in visual meteorological condition, and examination of the accident aircraft did not reveal any preexisting failure or malfunction to the aircraft or any of its systems. The accident aircraft propeller signatures that were found were consistent with the left propeller having been feathered, and the right propeller rotating upon impact.
Probable Cause: the pilot's failure to maintain Vmc, which resulted in a loss of control, and collision with the ground. Contributing to the accident was the pilot's decision to feather a propeller powered by an operational engine, while at a low altitude.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20001212X22029&key=1
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=3WT
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 27-Sep-2008 01:00 | ASN archive | Added |
| 05-Jun-2016 20:21 | Dr.John Smith | Updated [Time, Operator, Total fatalities, Total occupants, Other fatalities, Location, Country, Phase, Nature, Departure airport, Source, Damage, Narrative] |
| 21-Dec-2016 19:16 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:20 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 12-Dec-2017 19:12 | ASN Update Bot | Updated [Cn, Departure airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation