# NTSB WPR11LA068: Taylorcraft BC-65, N23619, Madras, OR, December 1, 2010

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: December 1, 2010, 11:30 local (19:30 UTC)
- Place: Madras, OR
- Coordinates: 44.670276, -121.154998 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=44.6703&lon=-121.1550&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining events: [Approach-VFR pattern final: Midair collision](https://openairdocs.org/ntsb-events/250); [Approach-VFR pattern final: Midair collision](https://openairdocs.org/ntsb-events/250)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report April 12, 2011
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: Portland FSDO
- NTSB case key (mKey): 77917
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR11LA068
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/77917/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=77917
- Page: https://openairdocs.org/ntsb/WPR11LA068

## Probable cause (aircraft 1)

The failure of both pilots to see and avoid the other airplane while in the traffic pattern to land, which resulted in a midair collision.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot (probable cause), aircraft 1; cases with it: [Taylorcraft BC-65, 1 case](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=8850306), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md)
- [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot of other aircraft (probable cause), aircraft 1; cases with it: [Taylorcraft BC-65, 1 case](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=8850306), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md)
- [Communications system: vHF communication system](https://openairdocs.org/ntsb-findings/01022312): Aircraft › Aircraft systems · Not specified, aircraft 1; cases with it: [Taylorcraft BC-65, 1 case](https://openairdocs.org/ntsb-findings/01022312/cases.md?model=8850306), [All aircraft, 6 cases](https://openairdocs.org/ntsb-findings/01022312/cases.md)
- [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot (probable cause), aircraft 2; cases with it: [Cessna 185A, 1 case](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=2072804), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md)
- [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot of other aircraft (probable cause), aircraft 2; cases with it: [Cessna 185A, 1 case](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=2072804), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach-VFR pattern final: Midair collision](https://openairdocs.org/ntsb-events/250) (defining event), aircraft 1; cases with it: [Taylorcraft BC-65, 1 case](https://openairdocs.org/ntsb-events/250/sequence.md?model=8850306), [All aircraft, 196 cases](https://openairdocs.org/ntsb-events/250/sequence.md)
- [Approach-VFR pattern final: Midair collision](https://openairdocs.org/ntsb-events/250) (defining event), aircraft 2; cases with it: [Cessna 185A, 1 case](https://openairdocs.org/ntsb-events/250/sequence.md?model=2072804), [All aircraft, 196 cases](https://openairdocs.org/ntsb-events/250/sequence.md)

## Analysis (aircraft 1)

The propeller of a Taylorcraft airplane and the empennage of a Cessna airplane came in contact with each other while both aircraft were on final approach to the same runway. The pilot of the Cessna had completed a landing and performed a standard entry (left) onto the downwind leg of the traffic pattern. The pilot of the Taylorcraft was returning from a local area training flight and entered the downwind leg of the traffic pattern from a standard mid-field 45-degree entry. The Cessna pilot was announcing his position on the common traffic advisory frequency during each segment of the pattern; however, the pilot of the Taylorcraft could not hear the transmissions since his airplane was not equipped with a radio. Just prior to impact, the pilot of the Taylorcraft observed the empennage of the Cessna underneath the left wing of his airplane. The pilot of the Cessna never observed the Taylorcraft, but heard a loud bang come from the aft end of his airplane at impact. Both pilots were able to land their airplanes without further incident.

## Factual narrative (aircraft 1)

On December 1, 2010, about 1130 Pacific standard time, the propeller of a Taylorcraft BC-65, N23619, and the aft portion of the empennage of a Cessna 185A, N1699Z, came in contact with each other while both aircraft were on a visual flight rules (VFR) final approach to runway 16 at Madras Municipal Airport, Madras, Oregon. The certified flight instructor (CFI) and his student in the Taylorcraft, which was not radio equipped, were not injured, but the airplane, which was owned and operated by Berg Air, sustained substantial damage to the forward part of its fuselage. The commercial pilot and his passenger in the Cessna were also uninjured, but the Cessna, which was owned and operated by the passenger, sustained substantial damage to its empennage and aft fuselage. The occupants of the Taylorcraft were on a 14 Code of Federal Regulation Part 91 local instructional flight, and the occupants of the Cessna were on a 14 Code of Federal Regulations personal pleasure flight. The pilot of the Cessna was on his second circuit of the VFR pattern to runway 16. The occupants of the Taylorcraft were on their first circuit of the VFR pattern to runway 16, after returning from a training flight in the local area and entering the pattern via a standard 45 degree entry to the downwind. Neither aircraft was on a flight plan. According to the flight instructor in the Taylorcraft, who was flying the airplane at the time of the accident, neither occupant had seen the Cessna until the empennage of the Cessna suddenly appeared underneath and very close to the left wing of his airplane while he was on short final. He said that at the precise moment that he noticed the Cessna, it seemed to slow, and as it did, its nose lowered and its tail pitched up. The CFI therefore immediately tried to bank to the right to avoid contact, but the propeller of the Taylorcraft came in contact with the Cessna before he could gain separation. After impacting the Cessna, the Taylorcraft's propeller stopped turning, and therefore the CFI made a power-off landing in the extended 1,800-foot paved stop-way of the old military runway. According to the pilot of the Cessna, who had announced his position on the common traffic advisory frequency (CTAF) on each segment of the traffic pattern, neither he nor his passenger ever saw the Taylorcraft, but while on short final he heard a loud bang come from the aft end of the airplane. Immediately after he heard the bang, the airplane pitched down and rolled to the right, but the pilot was able to regain control and continue flying straight ahead. Because he was unaware that the airplane had come in contact with another airplane, and because he thought the airplane had either impacted a large bird or experienced some sort of mechanical failure, he elected to climb straight ahead and land at the airplane's home airport, which was about 10 minutes away. It was not until after landing at the airplane's home airport and inspecting the airplane that the pilotof the Cessna realized there had been a mid-air collision. Both pilots had flown standard VFR left hand patterns for runway 16. The pilot of the Cessna entered the downwind from the crosswind after completing his first touch-and-go landing. The pilot of the Taylorcraft entered the downwind near mid-field from a 45 degree entry leg. The pilot of the Cessna was making position/intention radio calls at each segment of the pattern. The Taylorcraft was not radio-equipped, nor was it required to be. Therefore the pilot of the Taylorcraft was unable to announce his position/intentions, nor was he able to hear the transitions of the pilot of the Cessna. Neither occupant of either airplane noticed that there was another airplane in the VFR pattern at the same time as they were. At the time of the accident, there were broken clouds about 6,500 feet above ground level (AGL), and a visibility of more than 10 miles. Neither pilot reported any pre-impact anomalies or malfunctions associated with his airplane.

## Aircraft 1

- Registration: [N23619](https://openairdocs.org/aircraft/N23619), registered now, S/N 1344 (OpenAirDocs)
- Reported make and model: TAYLORCRAFT BC-65
- Registry model: [Taylorcraft BC-65](https://openairdocs.org/model/taylorcraft-bc-65) (registry code 8850306) (OpenAirDocs)
- Registry engine: [Lycoming 0-145B series](https://openairdocs.org/engine/lycoming-0-145b-series) (registry code 41502, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 1344
- Airframe hours: 2588
- Engines: LYCOMING O-145B SERIES 65 horsepower reciprocating
- Damage: Minor damage
- Flight: Instructional, Part 91
- Operator: Berg Air, doing business as Berg air
- Registered owner: Robert Berg
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, November 28, 2010
- Departed: S33, Madras, OR
- Destination: S33, Madras, OR
- Airport: S33, Madras Municipal Airport, runway 16, 5,089 × 75 ft, asphalt

## Aircraft 2

- Registration: [N1699Z](https://openairdocs.org/aircraft/N1699Z), registered now, S/N 1850499 (OpenAirDocs)
- Reported make and model: CESSNA 185A
- Registry model: [Cessna 185A](https://openairdocs.org/model/cessna-185a) (registry code 2072804) (OpenAirDocs)
- Registry engine: [Continental I0-470 series](https://openairdocs.org/engine/continental-i0-470-series) (registry code 17027, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 1850499
- Airframe hours: 2428
- Engines: CONT MOTOR IO-470 SERIES 260 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Weems John Scott
- Registered owner: Weems John Scott
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, May 1, 2010
- Departed: S33, Madras, OR
- Destination: S33, Madras, OR
- Airport: S33, Madras Municipal Airport, runway 16, 5,079 × 75 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Flight instructor, aircraft N23619; age 40; injuries: none; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, without waivers/limitations; last flight review March 11, 2010; seat: right; flight hours: 612 total, 17 in this make and model, 502 as pilot in command, 39 in the last 90 days, 6 in the last 30 days, 2 in the last 24 hours
- Pilot, aircraft N1699Z; age 36; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review August 12, 2010; seat: left; flight hours: 5,112 total, 4 in this make and model, 2,120 as pilot in command, 187 in the last 90 days, 70 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 170° at 10 knots
- Visibility: 10 statute miles
- Lowest ceiling: 6,500 ft broken
- Temperature: 45 °F, dew point 36 °F

## 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 20101201053192A](https://openairdocs.org/incident/20101201053192A), Dec 1, 2010: Taylorcraft BC-65, Madras, OR, Substantial damage. Both aircraft on short final at S33. Pilot of taylorcrft saw Cessna 185 tail slightly low and to left, tried to bank to right to avoid. Aircraft came together.…
- [Accident 20101201052502A](https://openairdocs.org/incident/20101201052502A), Dec 1, 2010: Cessna 185A, Madras, OR, Substantial damage. Both aircraft on short final at S33. Pilot of Taylorcraft saw Cessna 185 tail slightly low and to left, tried to bank to right to avoid. Aircraft came together…

## Docket (2 files)

The files NTSB released with the investigation on December 20, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=77917. 1.1 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (N23619) (item 1, .PDF, 547 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40340895&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20(N23619)-Redacted.PDF
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (N1699Z) (item 2, .PDF, 541 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40340896&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20(N1699Z)-Redacted.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; 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.