ASN Wikibase Occurrence # 20721
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 6 June 2008 |
| Time: | 17:45 |
| Type: |  Beechcraft A36 Bonanza |
| Owner/operator: | Private |
| Registration: | N27199 |
| MSN: | E-2321 |
| Year of manufacture: | 1986 |
| Total airframe hrs: | 2662 hours |
| Fatalities: | Fatalities: 0 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Pawtucket-North Central State Airport, RI (SFZ) -
 United States of America
|
| Phase: | Take off |
| Nature: | Private |
| Departure airport: | Smithfield-North Central Airport, RI (SFZ/KSFZ) |
| Morristown Municipal Airport, NJ (MMU/KMMU) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
A Beech A36, N27199, and a Piper PA-30, N7660Y, were substantially damaged during a runway collision at North Central State Airport (SFZ), Pawtucket, Rhode Island. The certificated private pilot and passenger of the Beech were not injured, and the certificated commercial pilot of the Piper sustained minor injuries.
Instrument meteorological conditions (IMC) prevailed at the time of the accident.
A Piper PA-30 was on an instrument flight rules (IFR) flight plan in instrument meteorological conditions and was cleared for an instrument approach. As the Piper approached the missed approach point, the pilot visually acquired the airport, and notified the air traffic controller to cancel his IFR flight plan. According to the Piper pilot, after the controller acknowledged the cancellation request, the pilot retuned his radio to the Common Traffic Advisory Frequency (CTAF) and announced his intention for landing. Due to the wind direction, the Piper pilot elected to circle and land on Runway 15, which was in the opposite direction of his approach. The pilot of a Beech A36, who was ready to depart from Runway 5 of the same airport, and who was also on an IFR flight plan, requested permission to take off but was told to "hold for release" by the controller. However, the controller did not explicitly inform the Beech pilot of the reason for the delay. Less than a minute later, the controller released the Beech. The two airplanes collided near the intersection of the two runways. Both pilots reported that they were not aware of the other airplane until immediately prior to the collision. Several witnesses heard the Beech pilot announce his intentions multiple times, but did not hear the Piper pilot's transmissions. The investigation also revealed that the two controllers were both aware of the proximity of the two airplanes, but neither one communicated that information to either of the pilots. A review of the recorded communications also revealed that the approach controller had a brief personal conversation with another controller just prior to the accident. The lack of received position or intent transmissions from the Piper, and the controllers' failure to inform the pilots of the proximity of the two airplanes, deprived the pilots of information that was critical to the pilots' situational awareness, and which could have enabled one or both pilots to prevent this accident.
Probable Cause: Both pilots' failure to see and avoid the other airplane. Contributing to the accident was the air traffic controllers failure to notify either pilot of the potential conflict.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 07-Jun-2008 08:00 | Fusko | Added |
| 20-Oct-2008 04:32 | RobertMB | Updated |
| 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] |
| 03-Dec-2017 11:23 | ASN Update Bot | Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
| 01-Dec-2023 07:51 | harro | Updated [Other fatalities, Departure airport, Destination airport, 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