# NTSB IAD00LA027: Bellanca 8KCAB, N2520Z, Erwinna, PA, March 18, 2000

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Limited investigation · Final report
- Date: March 18, 2000, 11:10 local (16:10 UTC)
- Place: Erwinna, PA
- Coordinates: 40.490432, -75.079544 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=40.4904&lon=-75.0795&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Highest injury: Minor injuries
- Injuries: 3 minor
- Status: Completed, report January 2, 2002
- Report: Approved by Office Director
- NTSB case key (mKey): 51170
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD00LA027
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/51170/pdf
- Page: https://openairdocs.org/ntsb/IAD00LA027

## Probable cause (aircraft 2)

the improper entry into the traffic pattern by the pilot of the Piper airplane and the inadequate lookout by the pilots in both airplanes.  A factor in the accident was that radio communication was not possible because the Piper was not so equipped, and the Bellanca's radios were turned off.

## Analysis (aircraft 2)

The flight instructor and private pilot flew the Bellanca airplane in the traffic pattern for several minutes, and were on the fourth approach to the runway at the time of the accident.  The private pilot said they flew a 'squared off traffic pattern' and were approximately 50 feet above ground level (agl) on final approach when the other airplane's shadow passed over.  The pilot of the Piper said he entered the traffic pattern on the downwind leg, but flew a modified base leg to final for noise abatement.  Witnesses described the Bellanca above and behind the Piper after both airplanes turned final.  They said the Bellanca overtook the Piper as it descended below the Piper in a slip.  Three witnesses said the Bellanca slowed, pitched up, and was struck from behind by the Piper.  One witness said the Bellanca's approach was on the runway heading, while the Piper's approach was '...tracking inbound left of the centerline on a slight angle.'  The crew turned off the Bellanca's radios after engine start, and the Piper was not equipped with a communication radio.  There was no locally published procedure for flight in and around the traffic pattern nor were there any depicted 'no fly' areas for purposes of noise abatement.  According to the Aeronautical Information Manual: 'When two or more aircraft are approaching an airport for the purpose of landing, the aircraft at the lower altitude has the right of way, but it shall not take advantage of this rule to cut in front of another which is on final approach to land, or to overtake that aircraft.'  Each pilot reported there were no mechanical deficiencies with their respective airplanes.

## Factual narrative (aircraft 2)

On March 18, 2000, at 1110 Eastern Standard Time, a Bellanca 8KCAB, N2520Z, and a Piper PA-25, N7460Z, were substantially damaged during a midair collision and subsequent collision with terrain at the Vansant Airport (9N1), Erwinna, Pennsylvania.  The certificated flight instructor and certificated private pilot in the Bellanca suffered minor injuries.  The certificated airline transport pilot in the Piper also suffered minor injuries.  Visual meteorological conditions prevailed.  The Piper was a local glider tow and the Bellanca was a local instructional flight.  Both flights originated at the Vansant Airport about 1100 and 1040, respectively.  No flight plan was filed for either flight conducted under 14 CFR Part 91.

During a telephone interview, the flight instructor said the purpose of the flight was to give flight instruction to the private pilot.  He said they departed 9N1, flew to a training area, practiced some maneuvers, and returned for some traffic pattern work.

The flight instructor said they were in the traffic pattern for several minutes and were on the fourth approach to Runway 07 at the time of the accident.  He said:

"We were on final and [the private pilot] started to pull the nose up to stretch his glide.  I told him, 'Don't do that.  Lower the nose and add power.'  All of a sudden there was this big 'clunk' and I said, 'What are you doing?'  At that point I took the controls, but they stopped working.  We hit the ground about 70 degrees nose down."

The flight instructor said the private pilot was unable to egress the airplane.  He said the fuel spilled as he coaxed and helped the pilot out of the airplane.  The flight instructor said it was several minutes before he was aware that another plane was involved and entangled with his own.

In a telephone interview, the private pilot gave an account of the flight consistent with that of his flight instructor.  He said that on the fourth approach, they flew a "squared off traffic pattern" and were approximately 50 feet above ground level (agl) on final approach when he become aware of the other airplane.  According to the private pilot:

"There was a shadow that passed over.  Then there was an impact and [the instructor] said, 'What was that?'  I knew at the jolt that we hit something.  The tail jerked to the left, the right wing dropped, and we went straight down."

In a telephone interview, the pilot in the Piper said he was returning after he towed a glider to 5,000 feet agl, 5 miles northeast of 9N1.  He said he entered a "normal" traffic pattern for practice, as he usually flies a more abbreviated pattern for noise abatement and to expedite glider towing.  According to the pilot:

"When I come off a tow, I do a pretty good wing over to check for traffic.  I usually do a split-S off a tow.  I arrived [at 9N1] about 1,000 feet agl east of the airport, and did about a 45-degree entry on the downwind.  I was practicing a standard pattern and it about killed me.  I checked traffic and made my base turn about three-quarters of a mile past the runway end.  I checked traffic, turned base, checked traffic, and turned final.  I'm looking out there and I don't see anything.  I turned final from a modified base for noise abatement."

The pilot said that once established on final approach, he was checking for vehicle traffic on the roadway at the approach end of runway 07.  He said the towrope was suspended several feet below the airplane on approach and that conflict with vehicle traffic was a concern.  According to the pilot:

"I'm getting ready to roll it on when, I felt a bump, I'm pulling back on the yoke, and the airplane's not coming up.  The next thing I know, I'm on the ground thinking, 'What the hell happened?'  I thought I broke an elevator cable."

According to the pilot, immediately after the accident, all three pilots involved compared stories and announced that they hadn't seen any other aircraft.  He said, "Three sets of eyes and nobody saw anything."

Three witnesses provided written statements.  Two witnesses described the Bellanca above and behind the Piper after both airplanes turned final.  They said the Bellanca overtook the Piper as it descended below the Piper in a slip.  Three witnesses said the Bellanca slowed, pitched up, and was struck from behind by the Piper.  One witness said the Decathlon's approach was on the runway heading, while the Piper's approach was "...tracking inbound left of the centerline on a slight angle."

When questioned, the private pilot of the Bellanca said the traffic pattern was 1,400 feet mean sea level (msl).  He said he did not know the altimeter setting at the time of the accident and that the altimeter was set to the field elevation at 9N1.  The private pilot said he turned on the aircraft communication radio during engine start, but turned it off 10 minutes into the flight at the suggestion of his flight instructor.

The pilot of the Piper said he was not equipped with a communication radio.  When questioned about the traffic pattern altitude, he said:

"One thousand feet agl.  We start out at zero because of the gliders, so everything is agl."

In a telephone interview, the airport manager said there was no locally published procedure for flight in an around the traffic pattern nor were there any depicted "no fly" areas for purposes of noise abatement.  He said:

"There is no published procedure.  The main complaint is from the tow planes.  We don't fly over the same houses every time.  Going east or north, we vary the departure.  We try to avoid houses we fly over all the time, generally on the turn from base to final."

According to the Aeronautical Information Manual:

"When two of more aircraft are approaching an airport for the purpose of landing, the aircraft at the lower altitude has the right of way, but it shall not take advantage of this rule to cut in front of another which is on final approach to land, or to overtake that aircraft."

Each pilot reported there were no mechanical deficiencies with their respective airplanes.

The pilot in the Piper reported 10,622 hours of flight experience, 1,986 hours of which were in the Piper PA-25.

The flight instructor reported approximately 14,000 hours of flight experience, with approximately 300 hours of experience in the Bellanca.

The private pilot reported 300 hours of total flight experience, with 2 hours of experience in the Bellanca.

At Doylestown (DYL), 9 miles northeast of 9N1, the winds were from 030 degrees at 8 knots in clear skies.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Midair collision, approach - vfr pattern - final approach
  - traffic pattern procedure - improper (cause)
  - visual lookout - inadequate, pilot of other aircraft (cause)
  - visual lookout - inadequate, pilot in command(cfi) (cause)
  - visual lookout - inadequate, dual student (cause)
  - radio communications - not possible, pilot in command(cfi) (contributing factor)
  - radio communications - not possible, pilot of other aircraft (contributing factor)
- In flight collision with terrain/water, descent - uncontrolled
- Midair collision, approach - vfr pattern - final approach
  - traffic pattern procedure - improper (cause)
  - visual lookout - inadequate, pilot in command (cause)
  - visual lookout - inadequate, pilot of other aircraft (cause)
  - radio communications - not possible, pilot in command (contributing factor)
  - radio communications - not possible, pilot of other aircraft (contributing factor)
- In flight collision with terrain/water, descent - uncontrolled

## Aircraft 1

- Registration: [N2520Z](https://openairdocs.org/deregistered/N2520Z-2000-08-15), registration cancelled 2000-08-15, S/N 336-77 (OpenAirDocs)
- Reported make and model: Bellanca 8KCAB
- Registry model: [Bellanca 8KCAB](https://openairdocs.org/model/bellanca-8kcab) (registry code 1220801) (OpenAirDocs)
- Category: Airplane
- Serial number: 336-77
- Airframe hours: 2129
- Engines: Lycoming AEIO-360-HIA 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Registered owner: Sport Aviation, Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, November 9, 1999, 40 hours before
- Departed: 9N1
- Airport: 9N1, Vansant Airport, runway 7, 3,058 × 120 ft, grass/turf

## Aircraft 2

- Registration: [N7460Z](https://openairdocs.org/aircraft/N7460Z), registered now, S/N 25-3457, built 1965 (OpenAirDocs)
- Reported make and model: Piper PA-25
- Registry model: [Piper PA-25-235](https://openairdocs.org/model/piper-pa-25-235) (registry code 7102504) (OpenAirDocs)
- Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 25-3457
- Airframe hours: 7593
- Engines: Lycoming O-540-B2C5 235 horsepower reciprocating
- Damage: Substantial damage
- Flight: Other work use, Part 91
- Registered owner: Sport Aviation, Inc
- Airworthiness certificate: Special, Restricted (Special)
- Last inspection: Annual, October 21, 1999, 79 hours before
- Departed: 9N1
- Airport: 9N1, Vansant Airport, runway 7, 3,058 × 120 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot, aircraft N2520Z; age 73; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: rear; flight hours: 14,000 total, 300 in this make and model, 13,800 as pilot in command, 150 in the last 90 days, 50 in the last 30 days, 1 in the last 24 hours
- Pilot, aircraft N7460Z; age 64; airline transport, flight instructor; airplane ratings: single-engine land, multi-engine sea, single-engine sea, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: center; flight hours: 10,622 total, 1,986 in this make and model, 10,390 as pilot in command, 13 in the last 90 days, 3 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 30° at 8 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 30 °F, dew point 7 °F
- Altimeter: 30.00 inHg
- Observed at: DYL, 9 nm away

## FAA reports on this event (2)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20000318006711A](https://openairdocs.org/incident/20000318006711A), Mar 18, 2000: Bbavia 8KCAB, Erwinna, PA, Substantial damage. (-23) Instructor and private pilot onboard decathalon N2520Z were on final approach to van sant airport (9N1) and were overtaken from behind and involved in…
- [Accident 20000318006712A](https://openairdocs.org/incident/20000318006712A), Mar 18, 2000: Piper PA25235, Erwinna, PA, Substantial damage. (-23) Instructor and private pilot onboard decathalon N2520Z were on final approach to van sant airport (9N1) and were overtaken from behind and involved in…

## Other investigations on N2520Z (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB NYC89LA112](https://openairdocs.org/ntsb/NYC89LA112), Apr 3, 1989: Champion 8KCAB (N2520Z), Manchester, NH, substantial damage. Probable cause: THE LOSS OF CONTROL AND COLLISION WITH A PARKED AIRCRAFT DUE TO THE INADVERTENT APPLICATION OF THE THROTTLE THAT TOOK PLACE AS THE PILOT WAS FASTENING THE OVER THE SHOULDER SAFETY HARNESS WHILE…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
