ASN Wikibase Occurrence # 30363
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 1 November 1999 |
| Time: | 07:16 LT |
| Type: |  Cessna T303 Crusader |
| Owner/operator: | Twin Cities Air Service Inc |
| Registration: | N511AR |
| MSN: | T30300192 |
| Year of manufacture: | 1982 |
| Total airframe hrs: | 5480 hours |
| Engine model: | Continental TSIO-520-AE |
| Fatalities: | Fatalities: 0 / Occupants: 3 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Binghamton Regional/Edwin A. Link Airport, Binghamton, NY -
 United States of America
|
| Phase: | En route |
| Nature: | Unknown |
| Departure airport: | Portland, ME (KPWM) |
| Youngstown, OH | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
While in cruise flight, at 6,000 feet, the left engine lost power. The pilot attempted a restart of the engine, but only about one-half rotation of the left engine propeller was observed, and the engine was secured. The pilot stated that he was unable to maintain altitude and initiated a decent. He requested and was cleared for an instrument approach at an airport where the weather conditions were, 1/4 statute mile of visibility, fog, and a vertical visibility of 100 feet. On the approach, at the minimum decent altitude, the pilot executed a missed approach. As the airplane climbed, the pilot reported to the controller that the 'best altitude [he] could get was 2,200 feet.' A second approach was initiated to the reciprocal runway. While on the second approach, the pilot 'was going to fly the aircraft right to the runway, and told the controller so.' He put the gear down, reduced power, and decided there was 'no hope for a go-around.' He then 'flew down past the decision height,' and about 70-80 feet above the ground, 'added a little power to smooth the landing.' The pilot also stated, 'The last thing I remember was the aircraft nose contacting the runway.' A passenger stated that once the pilot could not see the runway, [the pilot] 'applied power, pitched the nose up,' and attempted a 'go-around' similar to the one that was executed on the first approach. Disassembly of the left engine revealed that the crankshaft was fatigue fractured between connecting rod journal number 2 and main journal number 2. Review of the pilot's operating handbook revealed that the single engine service ceiling, at a weight of 4,800 pounds, was 11,700 feet. The average single engine rate of climb, at a pressure altitude of 6,000 feet, was 295 feet per minute. The average single engine rate of climb, at a pressure altitude of 1,625 feet, was 314 feet per minute. Review of the ILS approach plate for Runway 34 revealed that the decision height was 200 feet above the ground.
Probable Cause: The pilot's improper in-flight decision to descend below the decision height without the runway environment in sight, and his failure to execute a missed approach. A factor in the accident was the failed crankshaft.
Accident investigation:
 |
|
Sources:
NTSB NYC00FA023
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 27-Sep-2008 01:00 | ASN archive | Added |
| 10-Dec-2012 00:49 | onward | Updated [Time, Cn, Total fatalities, Total occupants, Other fatalities, Location, Country, Phase, Nature, Departure airport, Destination airport, Source, Damage, Narrative] |
| 14-Dec-2017 09:48 | ASN Update Bot | Updated [Time, Operator, Nature, Departure airport, Destination airport, Source, Damage, Narrative] |
| 07-Apr-2024 17:10 | ASN Update Bot | Updated [Time, Other fatalities, Phase, Departure airport, Destination airport, Source, Narrative, Category, Accident report] |
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