NYC08LA207

NTSB accident investigation · Beech A36 · Pawtucket, RI · June 6, 2008

Accident · Minor injuriesLimited investigationFinal report
Date
June 6, 2008, 17:45 local (21:45 UTC)
Place
Pawtucket, RI
Injuries
1 minor, 2 uninjured
Phase of flight
Takeoff
Aircraft
N27199Beech A36N7660YPiper PA-30
Defining events
Takeoff: Ground collisionLanding-landing roll: Ground collision
Weather
Instrument (IMC) · Day
Status
Completed · report March 3, 2010
Report
Approved by Office Director
Parties
FAA/FSDO
FAA report
20080606834709A
Case key
68183

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Findings · 10

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

N27199 · Beech A36

Action: lack of actionPersonnel issues › Action/decision · ATC personnelBeech A36: 8 casesAll aircraft: 792 casesProbable cause
Attention/monitoring: monitoring other aircraftPersonnel issues › Psychological · Pilot of other aircraftBeech A36: 4 casesAll aircraft: 231 casesProbable cause
Communication (personnel): lack of communicationPersonnel issues › Task performance · ATC personnelBeech A36: 3 casesAll aircraft: 84 casesProbable cause
Ceiling/visibility/precipEnvironmental issues › Conditions/weather/phenomena · Effect on operationBeech A36: 2 casesAll aircraft: 65 cases

N7660Y · Piper PA-30

Action: lack of actionPersonnel issues › Action/decision · ATC personnelPiper PA-30: 4 casesAll aircraft: 792 casesProbable cause
Ceiling/visibility/precipEnvironmental issues › Conditions/weather/phenomena · Effect on operationPiper PA-30: 2 casesAll aircraft: 65 cases
Attention/monitoring: monitoring other aircraftPersonnel issues › Psychological · Pilot of other aircraftPiper PA-30: 1 caseAll aircraft: 231 casesProbable cause
Communication (personnel): lack of communicationPersonnel issues › Task performance · ATC personnelPiper PA-30: 1 caseAll aircraft: 84 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

N7660Y · Piper PA-30

Analysis

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.

Factual narrative

History of flight

On June 6, 2008, about 1745 eastern daylight time, 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. The Beech was operating on an instrument flight rules (IFR) flight plan, and was departing SFZ for Morristown Municipal Airport (MMU), Morristown, New Jersey. The Piper was operating on an IFR flight plan from Nantucket Memorial Airport (ACK), Nantucket, Massachusetts, to SFZ. Both personal flights were conducted under the provisions of 14 Code of Federal Regulations (CFR) Part 91.

According to Federal Aviation Administration (FAA) air traffic control (ATC) transcripts, at 1718:56 the Piper pilot initially checked in on the radio frequency for Providence (PVD) Approach, reported that he was at four thousand feet, and requested the global positioning system (GPS) "Alpha" approach to SFZ. About 11 minutes later, the Beech pilot initially contacted PVD clearance delivery, and PVD clearance delivery responded. The Beech pilot then requested and was given his clearance, and at 1732:59, PVD clearance delivery responded with "november one nine nine and uh acknowledge holding for release please." At 1733:03 the Beech pilot acknowledged "yes holding for release ma'am."

At 1735:44, PVD approach transmitted the Piper's approach clearance, which was acknowledged by the pilot. One minute later, PVD approach issued the following instruction "twin comanche six zero yankee report cancellation of ifr in the air on this frequency or on the ground on one two four point three five change to advisory frequency approved," and at 1736:55 the Piper pilot responded with "sixty yank thank you sir." At 1737:43 the Beech pilot transmitted the following to PVD clearance delivery: "providence uh bonanza two seven one nine nine now we're holding next runway five uh ready to go [just need a release]." At 1737:57, PVD clearance responded "calling clearance was that november two seven one nine nine," and the Beech pilot responded "uh yes ma'am we're holding at runway five for departure uh one nine nine." A few seconds later, clearance delivery told the Beech pilot "november one nine nine hold for release i'll get back to you in approximately five minutes," and the Beech pilot responded with "one nine nine." Clearance delivery at 1738:11 "november one nine nine verify holding for release please," And 3 seconds later the Beech pilot responded "we're holding for release ma'am on nine nine."

At 1741:49, the Piper pilot cancelled his IFR flight plan, and then followed with another transmission that he had the airport in sight. Nine seconds later, PVD approach responded with "understand uh cancelling ifr november six zero yankee roger and uh squawk vfr frequency change approved good night." Four seconds after that, the Piper pilot acknowledged the instruction, and that was the last recorded transmission from the Piper.

Approximately one minute after the Piper pilot cancelled his IFR flight plan radar clearance delivery released the Beech for departure, with a clearance void time of five minutes. After his departure clearance was received, the Beech pilot switched his radio to the common traffic advisory frequency (CTAF), and broadcast his position and intentions twice. These broadcasts were confirmed by several witnesses located near a communication radio in a building on the airport. The Beech pilot then began his takeoff roll. About the same time, but unbeknownst to the Beech pilot, the Piper landed on runway 15.

According to the Piper pilot, as he approached the intersection of runway 5/23, at a speed of approximately 40 knots, he heard a noise outside the airplane, and saw the Beech on its takeoff roll on runway 5. According to the Beech pilot, as the airplane approached its rotation speed of 75 knots, the pilot and passenger saw the Piper approaching them from their left. The Beech pilot pulled back on the yoke in an attempt to fly over the Piper, but the airplanes collided with one another.

After the collision, which occurred when the Beech was airborne about 6 feet above the ground, the airplane descended back to the ground, veered off the runway, and came to a stop in the grass off the side of the runway. The Piper came to rest facing the opposite direction of travel, approximately 200 feet south of the runway 5 centerline, and approximately 20 feet off the pavement of runway 15.

Both pilots reported that neither one of them was aware that another airplane was operating at the airport until seconds prior to the collision.

Personnel information

Beech Pilot

The pilot, age 54, held a private pilot certificate, with ratings for airplane single-engine land and instrument airplane. His most recent FAA third-class medical certificate was issued on December 13, 2007. At the time of the accident, the pilot reported a total flight experience of 1,640 hours, including 1,000 hours as pilot in command in the accident airplane make and model, and 450 hours in instrument meteorological conditions. In the 90 days preceding the accident, the pilot logged 11 total hours of flight experience, and 3 hours of flight experience in IMC.

Piper Pilot

The pilot, age 45, held a commercial pilot certificate, with ratings for airplane single-engine land and instrument airplane, and private pilot privileges for airplane multi-engine land. At the time of the accident, the pilot reported a total flight experience of 3,215 hours, including 2,000 hours as pilot in command in the accident airplane make and model, and 418 hours of flight time in instrument meteorological conditions. In the 90 days preceding the accident, the pilot logged 62 total hours of flight experience and 7 hours of flight experience in IMC.

Aircraft information

Beech N27199

The Beech was a six seat, low wing, retractable-gear airplane, and was manufactured in 1986. It was powered by a Teledyne Continental Motors IO-550-B, 310-horsepower engine, and equipped with a McCauley controllable-pitch propeller. The airplane's most recent annual inspection was completed on October 2, 2007, and at the time of the accident the airplane had accumulated 2,662 total hours. The airplane was not equipped with a traffic alerting system.

Piper N7660Y

The Piper Comanche was a four seat, low wing, retractable-gear airplane, and was manufactured in 1965. It was powered by two Lycoming IO-320-B1A, 160-horsepower engines, equipped with Hartzell controllable pitch propellers. The most recent annual inspection was completed on April 1, 2008 and the airplane had accumulated 5,278.4 hours of total flight time at the time of inspection. The airplane was equipped with a Garmin GPS430W system which was installed in the airplane May 18, 2007. The airplane was not equipped with a traffic alerting system.

Meterological information

The 1735 recorded weather at SFZ reported calm winds, visibility 10 miles, an overcast cloud layer 600 feet above ground level (agl), temperature 14 degrees C, dew point 11 degrees C, and an altimeter setting of 30.13 inches of mercury.

A review of recorded weather observation at airports within a 30 mile radius of SFZ around the time of the accident showed the winds were out of the south and southwest and varied between 6 and 10 knots, and an overcast ceiling of between 500 and 900 feet agl.

Aids to naviagation

The published instrument approach procedure (IAP) for the very high omni-direction range (VOR)/GPS A approach to SFZ indicated that the minimum altitude at the final approach fix (FAF) was 1,900 feet mean sea level (msl), and the minimum descent altitude (MDA) for the approach was 980 feet msl, or 539 feet

Aircraft · 2

Registration
N27199
Reported as
Beech A36
Category
Airplane
Serial number
E-2321
Airframe hours
2,662
Engine
Teledyne Continental IO-550-8, 310 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · October 1, 2007
Departed
SFZ · Pawtucket, NJ
Destination
MMU · Morristown, NJ
Flight plan
IFR
Airport
SFZ · North Central Airport, runway 05, 5,000 × 100 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Registration
N7660Y
Reported as
Piper PA-30
Category
Airplane
Serial number
30-738
Airframe hours
5,278
Engines
Lycoming IO320B1A, 160 horsepower, reciprocatingLycoming IO320B1A, 160 horsepower, reciprocating
Damage
Substantial damage
Fire
On-Ground
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · April 1, 2008 · 50 hours before
Departed
ACK · Nantucket, MA
Destination
SFZ · Pawtucket, NJ
Flight plan
IFR
Airport
SFZ · North Central Airport, runway 15, 3,210 × 75 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot, aircraft N27199
Age
54
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
January 4, 2008
Seat
Left
Flight hours
1,640 total · 1,100 in this make and model · 1,492 as pilot in command · 11 in the last 90 days · 8 in the last 30 days
Role
Pilot, aircraft N7660Y
Age
45
Injuries
Minor
Certificates
Commercial, Private
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
June 1, 2007
Seat
Left
Flight hours
3,215 total · 2,965 in this make and model · 2,250 as pilot in command · 62 in the last 90 days · 34 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Instrument (IMC) · Day
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
600 ft overcast
Temperature
57 °F, dew point 52 °F
Altimeter
30.12 inHg
Observed at
SFZ

Docket · 15

The files NTSB released with the investigation on November 13, 2009, on NTSB’s docket system: statements, records, photos and specialists’ reports.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.