20010209004469A

Accident · No damage

FAA accident report · Bbavia 8KCAB · Leesburg, FL · February 9, 2001

Date
February 9, 2001 · 09:15 local
Place
Leesburg, FL
Airport
Leesburg Municipal Airport
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N123WA
NTSB investigation
NTSBMIA01FA074
Reported as
Bbavia 8KCAB
Fatal injuries
0

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) N123WA was struck from behind by an extra EA-300 after landing on rwy 13 at Leesburg. The events leading up to this ground collision are as follows: 1) N123WA, an American champion 8KCAB, was flying a long final approach to rwy 13 at Leesburg and made radio calls on the common traffic advisory frequency at 5 mi. Out, 3 mi. Out, and short final; 2) the EA-300 had been practicing takeoffs and short approaches in the apttern of rwy 13 for approximately 30 minutes prior to the arrival of the 8KCAB (the short approach procedure involves flying an oval pattern and descending rapidly throughout the downwind, base, and final legs); 3) the EA-300'S radio transmitter in use was not tuned to the proper common traffic advisory frequency (this frequency was changed a few months ago, and it was not published on the aeronauticalsectional chart nor was the new frequency available by checking the notices to airmen (NOTAMS) through the st. petersburg, Florida automated flight service station; 4) the EA-300'S pilot in command had just purchased the aircraft, and he was being administered a faimiliarization flight by the a/c salesman who held commercial pilot and flight instructor certificates the a/c salesman stated for the record that the buyer was the sole manipulator of the EA-300'S controls; 5) the EA-300'S PIC was from out of state and was not familar with Leesburg airport; 6) the wings of the EA-300 are attached at mid-fuselage and forward of the cockpit area, making downward and forward visibility poor for both occupants. The PIC sits in the rear seat; 7) the front seat occupant can speak with the pilot via intercom and he can hear radio transmissions, but he cannot see which frequency is tuned on the a/c's comm radios. Numerous witnesses reported that the EA-300 was flying an oval pattern and it was in a descending left turn from downwind, base, and final to runway 13. The 8KCAB, which was flying a long final, was at alower altitude and ahead of the EA-300 as the two a/c entered on very short final. The EA-300 was overtaking the 8KCAB. Probably the pilot of the EA-300 never saw the 8KCAB because his wing and his left descending turn blocked his downward and forward view. The 8KCAB with its high wings probably blocked the upward view its pilot would need to see the EA-300. Since the pilot of the 8KCAB did not hear any radio transmissions from the EA-300, he was not aware the EA-300 was present. By the time the 8KCAB touched down on the runway, the EA-300 was now about 25 feet behind him and ready to touch down with the distance still closing. The EA-300 touched down behind the decelerating 8KCAB and overtook him. The EA-300'S right wing struck the empennage of the 8KCAB and the EA-300'S propeller struck the left side of the 8KCAB'S fuselage. The 8KCAB was thrust up into the air and came to rest in an inverted position on the left side of the runway centerline. The EA-300 came to rest in an upright position on the right side of the runway edgeline.

As the FAA filed it

(-23) N123WA WAS STRUCK FROM BEHIND BY AN EXTRA EA-300 AFTER LANDING ON RWY 13 AT LEESBURG. THE EVENTS LEADING UP TO THIS GROUND COLLISION ARE AS FOLLOWS: 1) N123WA, AN AMERICAN CHAMPION 8KCAB, WAS FLYING A LONG FINAL APPROACH TO RWY 13 AT LEESBURG AND MADE RADIO CALLS ON THE COMMON TRAFFIC ADVISORY FREQUENCY AT 5 MI. OUT, 3 MI. OUT, AND SHORT FINAL; 2) THE EA-300 HAD BEEN PRACTICING TAKEOFFS AND SHORT APPROACHES IN THE APTTERN OF RWY 13 FOR APPROXIMATELY 30 MINUTES PRIOR TO THE ARRIVAL OF THE 8KCAB (THE SHORT APPROACH PROCEDURE INVOLVES FLYING AN OVAL PATTERN AND DESCENDING RAPIDLY THROUGHOUT THE DOWNWIND, BASE, AND FINAL LEGS); 3) THE EA-300'S RADIO TRANSMITTER IN USE WAS NOT TUNED TO THE PROPER COMMON TRAFFIC ADVISORY FREQUENCY (THIS FREQUENCY WAS CHANGED A FEW MONTHS AGO, AND IT WAS NOT PUBLISHED ON THE AERONAUTICALSECTIONAL CHART NOR WAS THE NEW FREQUENCY AVAILABLE BY CHECKING THE NOTICES TO AIRMEN (NOTAMS) THROUGH THE ST. PETERSBURG, FLORIDA AUTOMATED FLIGHT SERVICE STATION; 4) THE EA-300'S PILOT IN COMMAND HAD JUST PURCHASED THE AIRCRAFT, AND HE WAS BEING ADMINISTERED A FAIMILIARIZATION FLIGHT BY THE A/C SALESMAN WHO HELD COMMERCIAL PILOT AND FLIGHT INSTRUCTOR CERTIFICATES THE A/C SALESMAN STATED FOR THE RECORD THAT THE BUYER WAS THE SOLE MANIPULATOR OF THE EA-300'S CONTROLS; 5) THE EA-300'S PIC WAS FROM OUT OF STATE AND WAS NOT FAMILAR WITH LEESBURG AIRPORT; 6) THE WINGS OF THE EA-300 ARE ATTACHED AT MID-FUSELAGE AND FORWARD OF THE COCKPIT AREA, MAKING DOWNWARD AND FORWARD VISIBILITY POOR FOR BOTH OCCUPANTS. THE PIC SITS IN THE REAR SEAT; 7) THE FRONT SEAT OCCUPANT CAN SPEAK WITH THE PILOT VIA INTERCOM AND HE CAN HEAR RADIO TRANSMISSIONS, BUT HE CANNOT SEE WHICH FREQUENCY IS TUNED ON THE A/C'S COMM RADIOS. NUMEROUS WITNESSES REPORTED THAT THE EA-300 WAS FLYING AN OVAL PATTERN AND IT WAS IN A DESCENDING LEFT TURN FROM DOWNWIND, BASE, AND FINAL TO RUNWAY 13. THE 8KCAB, WHICH WAS FLYING A LONG FINAL, WAS AT ALOWER ALTITUDE AND AHEAD OF THE EA-300 AS THE TWO A/C ENTERED ON VERY SHORT FINAL. THE EA-300 WAS OVERTAKING THE 8KCAB. PROBABLY THE PILOT OF THE EA-300 NEVER SAW THE 8KCAB BECAUSE HIS WING AND HIS LEFT DESCENDING TURN BLOCKED HIS DOWNWARD AND FORWARD VIEW. THE 8KCAB WITH ITS HIGH WINGS PROBABLY BLOCKED THE UPWARD VIEW ITS PILOT WOULD NEED TO SEE THE EA-300. SINCE THE PILOT OF THE 8KCAB DID NOT HEAR ANY RADIO TRANSMISSIONS FROM THE EA-300, HE WAS NOT AWARE THE EA-300 WAS PRESENT. BY THE TIME THE 8KCAB TOUCHED DOWN ON THE RUNWAY, THE EA-300 WAS NOW ABOUT 25 FEET BEHIND HIM AND READY TO TOUCH DOWN WITH THE DISTANCE STILL CLOSING. THE EA-300 TOUCHED DOWN BEHIND THE DECELERATING 8KCAB AND OVERTOOK HIM. THE EA-300'S RIGHT WING STRUCK THE EMPENNAGE OF THE 8KCAB AND THE EA-300'S PROPELLER STRUCK THE LEFT SIDE OF THE 8KCAB'S FUSELAGE. THE 8KCAB WAS THRUST UP INTO THE AIR AND CAME TO REST IN AN INVERTED POSITION ON THE LEFT SIDE OF THE RUNWAY CENTERLINE. THE EA-300 CAME TO REST IN AN UPRIGHT POSITION ON THE RIGHT SIDE OF THE RUNWAY EDGELINE.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.