37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1009987 |
Time | |
Date | 201205 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | FCM.Airport |
State Reference | MN |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Cessna 400 |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Private |
Experience | Flight Crew Last 90 Days 50 Flight Crew Total 1510 Flight Crew Type 121 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural FAR Ground Incursion Runway |
Narrative:
Prior to arrival I briefed the runway diagram to fcm. After initial contact with tower at 10 miles out; I was told to expect runway 28L; and to report at three miles out. I could see both runways at this point; the light-colored runway 28L; and the dark-colored runway 28R. At 4 miles out; while flying a heading of about 310; the controller told me to fly north and to expect to land instead on runway 28R; as the was now other traffic bound for 28L. Shortly after turning north; I was told by tower that I was cleared to land on runway 28R. At this point I had a strong tailwind. I looked left to reacquire 28R visually; and I perceived that I had overshot 28R by a small amount; which I attributed to the tailwind on base. I continued the turn to final to realign with what I perceived to be 28R; and continued on to land on the runway. During the rollout; I informed tower where I would like to park; and the controller requested that I turn right on taxiway G and hold short of 28R. She then informed me of a possible pilot deviation. It was at this point that I realized that I had landed on the wrong runway. Factors that may have contributed to this could have included: 1) the relative infrequency of my flying to this airport; 2) the last minute request to change from 28L to 28R; while so close to the airport; 3) the fact that I apparently lost visual perception of 28R during turn from base to final; which I suspect may be related to it's darker color; and its blending into the surroundings; 4) my preconception that with a tailwind on base; I might overshoot the runway. In the future; especially with parallel runways; I will: 1) be particularly vigilant to confirm visually that I am aligned with the correct runway; 2) load the instrument approach; if available; so that I can have a localizer reference to either runway; 3) be sure to make a lasting mental note to runway variations in color or other visual cues; 4) be sure to confirm visually that I actually see the numbers; and right or left; when on short final.
Original NASA ASRS Text
Title: Confused by the Tower's changes in landing runway assignments and experiencing difficulty in maintaining visual awareness of the two parallel runways as distinct from long; more clearly defined parallel taxiways; the pilot of a Cessna 400 landed on Runway 28L at FCM instead of 28R as cleared.
Narrative: Prior to arrival I briefed the runway diagram to FCM. After initial contact with Tower at 10 miles out; I was told to expect Runway 28L; and to report at three miles out. I could see both runways at this point; the light-colored Runway 28L; and the dark-colored Runway 28R. At 4 miles out; while flying a heading of about 310; the Controller told me to fly north and to expect to land instead on Runway 28R; as the was now other traffic bound for 28L. Shortly after turning north; I was told by Tower that I was cleared to land on Runway 28R. At this point I had a strong tailwind. I looked left to reacquire 28R visually; and I perceived that I had overshot 28R by a small amount; which I attributed to the tailwind on base. I continued the turn to final to realign with what I perceived to be 28R; and continued on to land on the runway. During the rollout; I informed Tower where I would like to park; and the Controller requested that I turn right on Taxiway G and hold short of 28R. She then informed me of a possible pilot deviation. It was at this point that I realized that I had landed on the wrong runway. Factors that may have contributed to this could have included: 1) the relative infrequency of my flying to this airport; 2) the last minute request to change from 28L to 28R; while so close to the airport; 3) the fact that I apparently lost visual perception of 28R during turn from base to final; which I suspect may be related to it's darker color; and its blending into the surroundings; 4) my preconception that with a tailwind on base; I might overshoot the runway. In the future; especially with parallel runways; I will: 1) be particularly vigilant to confirm visually that I am aligned with the correct runway; 2) load the instrument approach; if available; so that I can have a localizer reference to either runway; 3) be sure to make a lasting mental note to runway variations in color or other visual cues; 4) be sure to confirm visually that I actually see the numbers; and R or L; when on short final.
Data retrieved from NASA's ASRS site as of July 2013 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.