 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Close proximity GA small aircraft on takeoff roll and GA small aircraft making a go around because the other aircraft had cut him off.
| Attributes | |
| ACN | 150935 |
| Time | |
| Date | 199007 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : l39 |
| State Reference | CA |
| 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 | climbout : takeoff |
| Flight Plan | None |
| Aircraft 2 | |
| Operator | general aviation : personal |
| Make Model Name | Small Aircraft |
| Flight Phase | descent other landing : go around |
| Flight Plan | None |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : private |
| Experience | flight time last 90 days : 12 flight time total : 130 flight time type : 130 |
| ASRS Report | 150935 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Events | |
| Anomaly | conflict : ground critical non adherence : far other spatial deviation |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : took evasive action other |
| Consequence | Other |
| Miss Distance | horizontal : 0 vertical : 200 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | other |
Narrative:
Recently ramona airport changed their CTAF/unicom frequency from 122.8 to 122.7 I had been flying to other uncontrolled fields whose CTAF was 122.8, and where they typically would not respond to a request for traffic advisories. When I headed for ramona I wasn't really too surprised when I recieved no response to my landing advisory request while still on 122.8. I made an uneventful landing and taxied back for takeoff and waited for traffic on final to land. Upon taking the active and beginning my takeoff roll, I noticed an small aircraft biplane over-flying the runway. It was at that point that I realized that I was tuned to the wrong frequency, and I hadn't seen the small aircraft Y because he had made right traffic from the aerobatic area north of the field. Obviously my not receiving replys had created an expectation of continued radio silence. I had also taken for granted that other pilots would make left traffic and I did not scan 360 degrees before taking the active runway.
Original NASA ASRS Text
Title: CLOSE PROX GA SMA ON TKOF ROLL AND GA SMA MAKING A GO AROUND BECAUSE THE OTHER ACFT HAD CUT HIM OFF.
Narrative: RECENTLY RAMONA ARPT CHANGED THEIR CTAF/UNICOM FREQ FROM 122.8 TO 122.7 I HAD BEEN FLYING TO OTHER UNCTLED FIELDS WHOSE CTAF WAS 122.8, AND WHERE THEY TYPICALLY WOULD NOT RESPOND TO A REQUEST FOR TFC ADVISORIES. WHEN I HEADED FOR RAMONA I WASN'T REALLY TOO SURPRISED WHEN I RECIEVED NO RESPONSE TO MY LNDG ADVISORY REQUEST WHILE STILL ON 122.8. I MADE AN UNEVENTFUL LNDG AND TAXIED BACK FOR TKOF AND WAITED FOR TFC ON FINAL TO LAND. UPON TAKING THE ACTIVE AND BEGINNING MY TKOF ROLL, I NOTICED AN SMA BIPLANE OVER-FLYING THE RWY. IT WAS AT THAT POINT THAT I REALIZED THAT I WAS TUNED TO THE WRONG FREQ, AND I HADN'T SEEN THE SMA Y BECAUSE HE HAD MADE R TFC FROM THE AEROBATIC AREA N OF THE FIELD. OBVIOUSLY MY NOT RECEIVING REPLYS HAD CREATED AN EXPECTATION OF CONTINUED RADIO SILENCE. I HAD ALSO TAKEN FOR GRANTED THAT OTHER PLTS WOULD MAKE L TFC AND I DID NOT SCAN 360 DEGS BEFORE TAKING THE ACTIVE RWY.
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.