37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1428304 |
Time | |
Date | 201702 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | CNO.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 87 Flight Crew Total 5230 Flight Crew Type 278 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Unstabilized Approach |
Narrative:
I was assigned right downwind for landing on 26R at cno. Instructed to follow an aircraft on a three mile final. I extended my downwind looking for the traffic. I identified traffic and turned on my base leg. As I turned final I was focused on the aircraft ahead of me wanting to insure I had proper spacing. As the aircraft landed and I approached the runway; I realized I had mistakenly identified an aircraft which was landing on 26L. Just as I was beginning my correction I was advised by the tower that I was lined up on 26L and had been cleared to land on 26R. I acknowledged and informed the controller I was correcting and would do a go around for landing on 26R. I was cleared for right traffic pattern and cleared to land on 26R. I continued right traffic and landed 26R without incident and felt there was no aircraft spacing violated. As a flight instructor I have probably landed at this airport a thousand times. I realize that a certain amount of this issue was focusing on the other aircraft and not my total surroundings. A good lesson on why we should treat every landing as a go around possibility.
Original NASA ASRS Text
Title: Small fixed wing pilot reported mistakenly following traffic towards the parallel runway; was advised of his error and executed a go around.
Narrative: I was assigned right downwind for landing on 26R at CNO. Instructed to follow an aircraft on a three mile final. I extended my downwind looking for the traffic. I identified traffic and turned on my base leg. As I turned final I was focused on the aircraft ahead of me wanting to insure I had proper spacing. As the aircraft landed and I approached the runway; I realized I had mistakenly identified an aircraft which was landing on 26L. Just as I was beginning my correction I was advised by the tower that I was lined up on 26L and had been cleared to land on 26R. I acknowledged and informed the controller I was correcting and would do a go around for landing on 26R. I was cleared for right traffic pattern and cleared to land on 26R. I continued right traffic and landed 26R without incident and felt there was no aircraft spacing violated. As a Flight Instructor I have probably landed at this airport a thousand times. I realize that a certain amount of this issue was focusing on the other aircraft and not my total surroundings. A good lesson on why we should treat every landing as a go around possibility.
Data retrieved from NASA's ASRS site 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.