37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 914298 |
Time | |
Date | 201010 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | YKM.Airport |
State Reference | WA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Sport Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Commercial Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 30 Flight Crew Total 1620 Flight Crew Type 112 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Miss Distance | Horizontal 1500 Vertical 0 |
Narrative:
I intended a short recreational flight from ykm to the foothills about 10 NM northwest and back. I requested taxi for takeoff with ATIS information golf; VFR departure northwest; 'from intersection alpha 3; if available.' current ATIS advised runway 9 in use. Ground instructed me to taxi 'to runway 27; intersection alpha 3; via alpha.' I completed a run-up at A3; switched to tower frequency; and advised 'experimental xx ready at alpha 3.' I deliberately did not specify the runway because there was a light crosswind from the south-southeast; there was an aircraft about to enter a right downwind for runway 9; and although I had been instructed to runway 27; I thought the controller might switch me to runway 9. On the other hand; I thought he may have given me runway 27 for an easy transition to a northwest heading. The clearance was 'experimental xx ; without delay; cleared for takeoff on runway 27.' I confirmed; 'experimental xx; cleared for takeoff; runway 27.' I did not challenge the assignment; even though my gut didn't feel it was correct. In my takeoff climb; just over the numbers; I noticed the other aircraft abeam on a right downwind for runway 9 and thought; 'this is a mistake.' immediately; the controller called; 'experimental xx; you were cleared for runway 9; continue on course.' I replied; 'I was given runway 27; sir.' he instructed me to turn right. It was not a near miss situation; but separation was reducing. When I called for landing instructions about a half hour later the controller assigned straight in for runway 9 and said; 'you can call me at the tower. I owe you an apology.' after I landed; we had a cordial phone conversation; in which the controller stated they had 'played the tapes' and repeated his apology. My lesson was to trust my gut and challenge (or at least re-confirm) an assignment that doesn't feel right. I think a contributing factor was the added stress on controllers due to the runway being under construction for a month for repaving; with alternating displaced thresholds and constant equipment and personnel accessing the runway during aircraft operations. I think airport management needs to better address safety issues arising from extended periods of runway disruption. At the time of this event; the last 2;500 ft of runway 9 was out of service.
Original NASA ASRS Text
Title: Light sport pilot reports being instructed to taxi to Runway 27 although ATIS was advertising Runway 9; with traffic on downwind for Runway 9. The Tower Controller thought he had issued instructions for Runway 9 but apologized after reviewing the tapes.
Narrative: I intended a short recreational flight from YKM to the foothills about 10 NM northwest and back. I requested taxi for takeoff with ATIS information Golf; VFR departure northwest; 'from Intersection Alpha 3; if available.' Current ATIS advised Runway 9 in use. Ground instructed me to taxi 'to Runway 27; Intersection Alpha 3; via Alpha.' I completed a run-up at A3; switched to Tower frequency; and advised 'Experimental XX ready at Alpha 3.' I deliberately did not specify the runway because there was a light crosswind from the south-southeast; there was an aircraft about to enter a right downwind for Runway 9; and although I had been instructed to Runway 27; I thought the Controller might switch me to Runway 9. On the other hand; I thought he may have given me Runway 27 for an easy transition to a northwest heading. The clearance was 'Experimental XX ; without delay; cleared for takeoff on Runway 27.' I confirmed; 'Experimental XX; cleared for takeoff; Runway 27.' I did not challenge the assignment; even though my gut didn't feel it was correct. In my takeoff climb; just over the numbers; I noticed the other aircraft abeam on a right downwind for Runway 9 and thought; 'This is a mistake.' Immediately; the Controller called; 'Experimental XX; you were cleared for Runway 9; continue on course.' I replied; 'I was given Runway 27; sir.' He instructed me to turn right. It was not a near miss situation; but separation was reducing. When I called for landing instructions about a half hour later the Controller assigned straight in for Runway 9 and said; 'You can call me at the Tower. I owe you an apology.' After I landed; we had a cordial phone conversation; in which the Controller stated they had 'played the tapes' and repeated his apology. My lesson was to trust my gut and challenge (or at least re-confirm) an assignment that doesn't feel right. I think a contributing factor was the added stress on Controllers due to the runway being under construction for a month for repaving; with alternating displaced thresholds and constant equipment and personnel accessing the runway during aircraft operations. I think airport management needs to better address safety issues arising from extended periods of runway disruption. At the time of this event; the last 2;500 FT of Runway 9 was out of service.
Data retrieved from NASA's ASRS site as of April 2012 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.