 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Mooney M20D pilot entered the traffic pattern on the wrong side of the runway at an uncontrolled airport. Another pilot hearing reporter's announcement advised him of the correct traffic pattern.
| Attributes | |
| ACN | 515805 |
| Time | |
| Date | 200106 |
| Day | Tue |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : 002.airport |
| State Reference | CO |
| Altitude | msl single value : 5600 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : ues.tower |
| Operator | general aviation : personal |
| Make Model Name | M-20 D Master |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach |
| Flight Plan | None |
| Aircraft 2 | |
| Operator | Other |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | other : unk |
| Flight Phase | other |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : commercial |
| Experience | flight time last 90 days : 0.5 flight time total : 5667 flight time type : 413 |
| ASRS Report | 515805 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | other spatial deviation |
| Independent Detector | other flight crewb |
| Resolutory Action | flight crew : returned to intended or assigned course other |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Airspace Structure Airport |
| Primary Problem | Flight Crew Human Performance |
Narrative:
Prior to arriving at ftg, I called CTAF 123.0 with a position report and asked what their wind and active runway was. After several calls with no reply, and there was no traffic in the area, I reported that I was entering a left downwind for runway 8 for a touch-and-go. I was on a 1/4 mi final when an arriving pilot stated that runway 8 was right traffic. I changed to right traffic on future lndgs. No conflicts were caused. There was moderate turbulence at the time and I missed the notation on the chart that runway 8 was right traffic. I should have checked this during my flight planning before takeoff of the flight. I will be taking some dual flight instruction along with a BFR in a few days. There was no conflict with any aircraft arriving or departing ftg. At this time, I realize that every small detail needs to be checked on preflight prior to takeoff.
Original NASA ASRS Text
Title: MOONEY M20D PLT ENTERED THE TFC PATTERN ON THE WRONG SIDE OF THE RWY AT AN UNCTLED ARPT. ANOTHER PLT HEARING RPTR'S ANNOUNCEMENT ADVISED HIM OF THE CORRECT TFC PATTERN.
Narrative: PRIOR TO ARRIVING AT FTG, I CALLED CTAF 123.0 WITH A POS RPT AND ASKED WHAT THEIR WIND AND ACTIVE RWY WAS. AFTER SEVERAL CALLS WITH NO REPLY, AND THERE WAS NO TFC IN THE AREA, I RPTED THAT I WAS ENTERING A L DOWNWIND FOR RWY 8 FOR A TOUCH-AND-GO. I WAS ON A 1/4 MI FINAL WHEN AN ARRIVING PLT STATED THAT RWY 8 WAS R TFC. I CHANGED TO R TFC ON FUTURE LNDGS. NO CONFLICTS WERE CAUSED. THERE WAS MODERATE TURB AT THE TIME AND I MISSED THE NOTATION ON THE CHART THAT RWY 8 WAS R TFC. I SHOULD HAVE CHKED THIS DURING MY FLT PLANNING BEFORE TKOF OF THE FLT. I WILL BE TAKING SOME DUAL FLT INSTRUCTION ALONG WITH A BFR IN A FEW DAYS. THERE WAS NO CONFLICT WITH ANY ACFT ARRIVING OR DEPARTING FTG. AT THIS TIME, I REALIZE THAT EVERY SMALL DETAIL NEEDS TO BE CHKED ON PREFLT PRIOR TO TKOF.
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.