37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 246296 |
Time | |
Date | 199306 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : 218 |
State Reference | OH |
Altitude | agl bound lower : 0 agl bound upper : 5 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | other |
Make Model Name | Helicopter |
Flight Phase | cruise other landing other |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | climbout : takeoff |
Flight Plan | None |
Person 1 | |
Affiliation | government : military |
Function | instruction : instructor oversight : pic |
Qualification | pilot : military pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 35 flight time total : 1075 flight time type : 200 |
ASRS Report | 246296 |
Person 2 | |
Affiliation | government : military |
Function | flight crew : single pilot instruction : trainee |
Qualification | pilot : military |
Events | |
Anomaly | conflict : ground critical conflict : nmac incursion : runway non adherence : far non adherence : published procedure other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action |
Consequence | Other |
Miss Distance | horizontal : 100 vertical : 5 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
As I approached 2i8 airport, 10 mi to the ssw, I called position, altitude and requested advisories on 122.7 unicom/CTAF. There were no calls from any traffic on the airfield. At 5 mi out, I made another call requesting advisories again, there were no answers. Upon entry to a left downwind for runway 27, I again announced my actions and location. At the same time, I descended to 700 ft AGL (1500 ft MSL) for traffic pattern altitude. As I began a left turn for base, an announcement of my actions was made, again no replies. Upon completion of final approach, an announcement was made of my actions. The VASI was used for the approach, therefore, terminating the approach to a hover just past the numbers. I then began hovering toward midfield when I noticed the profile of a red small aircraft Y taking off toward me (runway 9). I then hover-taxied to the north side. After reconfirming the correct frequency for the unicom, I then proceeded to perform a communication check, which was confirmed by a different aircraft on the field. The reason I had landed on runway 27 is because the predominant winds were in the general area of 300 degrees.
Original NASA ASRS Text
Title: NMAC BTWN SMA AND ROTARY WINGED TFC IN AN OPPOSITE DIRECTION TFC SIT.
Narrative: AS I APCHED 2I8 ARPT, 10 MI TO THE SSW, I CALLED POS, ALT AND REQUESTED ADVISORIES ON 122.7 UNICOM/CTAF. THERE WERE NO CALLS FROM ANY TFC ON THE AIRFIELD. AT 5 MI OUT, I MADE ANOTHER CALL REQUESTING ADVISORIES AGAIN, THERE WERE NO ANSWERS. UPON ENTRY TO A L DOWNWIND FOR RWY 27, I AGAIN ANNOUNCED MY ACTIONS AND LOCATION. AT THE SAME TIME, I DSNDED TO 700 FT AGL (1500 FT MSL) FOR TFC PATTERN ALT. AS I BEGAN A L TURN FOR BASE, AN ANNOUNCEMENT OF MY ACTIONS WAS MADE, AGAIN NO REPLIES. UPON COMPLETION OF FINAL APCH, AN ANNOUNCEMENT WAS MADE OF MY ACTIONS. THE VASI WAS USED FOR THE APCH, THEREFORE, TERMINATING THE APCH TO A HOVER JUST PAST THE NUMBERS. I THEN BEGAN HOVERING TOWARD MIDFIELD WHEN I NOTICED THE PROFILE OF A RED SMA Y TAKING OFF TOWARD ME (RWY 9). I THEN HOVER-TAXIED TO THE N SIDE. AFTER RECONFIRMING THE CORRECT FREQ FOR THE UNICOM, I THEN PROCEEDED TO PERFORM A COM CHK, WHICH WAS CONFIRMED BY A DIFFERENT ACFT ON THE FIELD. THE REASON I HAD LANDED ON RWY 27 IS BECAUSE THE PREDOMINANT WINDS WERE IN THE GENERAL AREA OF 300 DEGS.
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.