ASN Wikibase Occurrence # 26397
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: | Wednesday 14 August 1996 |
| Time: | 07:08 LT |
| Type: |  Piper PA-31T Cheyenne II |
| Owner/operator: | Basco Flying Service Inc&pa |
| Registration: | N163SA |
| MSN: | 31T-7920025 |
| Year of manufacture: | 1979 |
| Total airframe hrs: | 4993 hours |
| Engine model: | P&W PT6A-28 |
| Fatalities: | Fatalities: 0 / Occupants: 3 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Pottstown Municipal Airport, in Pottstown, Pennsylvania. -
 United States of America
|
| Phase: | Take off |
| Nature: | Unknown |
| Departure airport: | , PA (N47) |
| Philadelphia, PA (PHL | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
During an attempted takeoff, the airplane collided with a taxiway sign, a fence, a light pole and came to rest between two buildings. According to the pilot in command (seated in the right seat), a preflight and run-up inspection was completed successfully. He stated that a pilot rated passenger (in the left front seat) was following along with a placard checklist. He stated that the airplane was accelerated for takeoff on runway 7, and at 500 feet down the 2700 foot long runway with the airspeed at redline, rotation was initiated and the airplane veered to the right. He stated that shortly thereafter the right engine surged and he noted the matched power levers, but he did not record the engine power instruments. A passenger (seated in a forward facing seat behind the pilot in command) reported that the pilot rated passenger's hand was on the throttle(yellow-knobbed handles) at the time of the accident The reported visibility was 1/8 mile in fog. The prescribed takeoff minimums for that airport is 400 feet and 1 mile visibility. Postaccident examination of the engines and their systems revealed no evidence of preimpact mechanical malfunction. The pilot reported that there was no mechanical malfunction.
Probable Cause: The pilot's failure to maintain directional control during takeoff/ground run resulting in in-flight collision with a fence. Related factors were the pilot's poor planning/decision making, and the fog.
Accident investigation:
 |
|
Sources:
NTSB IAD96LA133
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=163SA
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 27-Sep-2008 01:00 | ASN archive | Added |
| 21-Dec-2016 19:14 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 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] |
| 20-May-2017 18:37 | TB | Updated [Cn, Source, Narrative] |
| 07-Aug-2017 08:39 | TB | Updated [Aircraft type, Cn] |
| 13-Sep-2017 19:30 | Dr. John Smith | Updated [Time, Operator, Location, Phase, Nature, Departure airport, Destination airport, Source, Narrative] |
| 08-Apr-2024 19:33 | ASN Update Bot | Updated [Time, Operator, Other fatalities, Nature, 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