37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 195824 |
Time | |
Date | 199112 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : zzv |
State Reference | OH |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | ground : holding ground : preflight ground other : taxi |
Flight Plan | None |
Aircraft 2 | |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | descent : approach landing other |
Flight Plan | None |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : single pilot |
Qualification | pilot : commercial pilot : instrument pilot : cfi |
Experience | flight time last 90 days : 130 flight time total : 5883 flight time type : 752 |
ASRS Report | 195824 |
Person 2 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Events | |
Anomaly | conflict : ground critical other spatial deviation |
Independent Detector | other other : unspecified cockpit |
Resolutory Action | flight crew : rejected takeoff |
Consequence | Other |
Miss Distance | horizontal : 100 vertical : 50 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Prior to entering runway 04 at zzv for a student training flight in an small aircraft we made a left hand 360 degree turn to clear the pattern for traffic, held short of the runway to clear final, announced our intentions to depart runway 04, taxied onto the runway and began a takeoff roll. Shortly into the takeoff roll, 2 single engine high wing tailwheel aircraft passed over us, 1 to each side of the runway at what I considered extremely close to us and to 1 another at an unusually low altitude no further than 50 ft AGL. We immediately aborted the takeoff and exited the runway. 1 aircraft made a tight left turn and landed almost immediately after we had taxied clear; the other entered the pattern and landed shortly after. At no time prior to our entering the runway did we receive any radio transmissions from traffic inbound or in the pattern at zzv; and no aircraft were visible to us when we cleared the area prior to entering the runway. I did not see either aircraft until the flew over us, apparently in formation. I believe that neither aircraft were flying a standard traffic pattern and that and the fact that neither gave a position report over the radio contributed to my and my student's inability to see them prior to entering the runway and resulted in the incident. I believe that the incident could have been avoided if standard traffic reports had been made and (particularly in the case of a no radio aircraft) a standard traffic pattern had been flown. More emphasis on standardized traffic pattern procedures and reports, and adhering to current published procedures may help avoid future incidents such as this one.
Original NASA ASRS Text
Title: INSTRUCTOR WITH STUDENT IN SMA CLRED AREA BUT SHORTLY INTO TKOF ROLL HAD 2 SMA ACFT PASS OVERHEAD ONE ON EITHER SIDE. RPTR PROTESTS CLOSE PASS BY THE 2 ACFT.
Narrative: PRIOR TO ENTERING RWY 04 AT ZZV FOR A STUDENT TRAINING FLT IN AN SMA WE MADE A L HAND 360 DEG TURN TO CLR THE PATTERN FOR TFC, HELD SHORT OF THE RWY TO CLR FINAL, ANNOUNCED OUR INTENTIONS TO DEPART RWY 04, TAXIED ONTO THE RWY AND BEGAN A TKOF ROLL. SHORTLY INTO THE TKOF ROLL, 2 SINGLE ENG HIGH WING TAILWHEEL ACFT PASSED OVER US, 1 TO EACH SIDE OF THE RWY AT WHAT I CONSIDERED EXTREMELY CLOSE TO US AND TO 1 ANOTHER AT AN UNUSUALLY LOW ALT NO FURTHER THAN 50 FT AGL. WE IMMEDIATELY ABORTED THE TKOF AND EXITED THE RWY. 1 ACFT MADE A TIGHT L TURN AND LANDED ALMOST IMMEDIATELY AFTER WE HAD TAXIED CLR; THE OTHER ENTERED THE PATTERN AND LANDED SHORTLY AFTER. AT NO TIME PRIOR TO OUR ENTERING THE RWY DID WE RECEIVE ANY RADIO TRANSMISSIONS FROM TFC INBOUND OR IN THE PATTERN AT ZZV; AND NO ACFT WERE VISIBLE TO US WHEN WE CLRED THE AREA PRIOR TO ENTERING THE RWY. I DID NOT SEE EITHER ACFT UNTIL THE FLEW OVER US, APPARENTLY IN FORMATION. I BELIEVE THAT NEITHER ACFT WERE FLYING A STANDARD TFC PATTERN AND THAT AND THE FACT THAT NEITHER GAVE A POS RPT OVER THE RADIO CONTRIBUTED TO MY AND MY STUDENT'S INABILITY TO SEE THEM PRIOR TO ENTERING THE RWY AND RESULTED IN THE INCIDENT. I BELIEVE THAT THE INCIDENT COULD HAVE BEEN AVOIDED IF STANDARD TFC RPTS HAD BEEN MADE AND (PARTICULARLY IN THE CASE OF A NO RADIO ACFT) A STANDARD TFC PATTERN HAD BEEN FLOWN. MORE EMPHASIS ON STANDARDIZED TFC PATTERN PROCS AND RPTS, AND ADHERING TO CURRENT PUBLISHED PROCS MAY HELP AVOID FUTURE INCIDENTS SUCH AS THIS ONE.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.