37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1740532 |
Time | |
Date | 202004 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | None |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural FAR |
Narrative:
The objective for this particular flight was recurrent formation training for me; with the assistance of the pilot of a second aircraft (an occasional training partner; based at another nearby airport). Per our telephonic briefing on the ground; we agreed that we would rendezvous in a particular location and that he would fly lead and I would join off his wing there. We further agreed on a time; altitude; frequency and call signs.as I approached the practice area I observed at my 12 o'clock position at approximately 3;500 MSL an [aircraft Y type] heading in the same direction -- i.e. To the center of the practice area.on the air-to-air frequency; I then made my first call to check in and to ask the flight lead if he was in position. He responded that he was approaching the practice area. I told him I thought I had him in sight.he then asked me my position; and I said I was at his 6 o'clock; several miles in trail. I told him he could maintain his heading and I would close from the rear.as I approached the [aircraft Y type] in front of me; I suggested over the air-to-air frequency that my training partner make a shallow turn to help me close; and he acknowledged. A moment later; the [aircraft Y type] in front of me began a gentle turn to the left.once I was established in the turn and began to close; my partner asked for my current position; I indicated that I was moving from trail to his right wing. During this time I moved into a loose fingertip off the lead aircraft. About this time my partner asked again for my position and said he could not see me. I replied that I was off his right wing; and thought for a moment that possibly I was partly blocked by the window/door framing. To help with his field of view; I moved slightly forward to a more visible bearing line; and then radioed to ask if he had a clear visual. He responded that he still did not; and at that point it suddenly occurred to me that I might be flying formation off the wrong aircraft. Over the air-to-air frequency I read the north number of the [aircraft Y type] in view; and asked if that was my training partner's aircraft (we had been using call signs; so I had not had any prior occasion to reference his north number). He replied that he was flying a different aircraft; and the mistaken identity suddenly was clear to us both.at the point; I broke off formation with the [aircraft Y type]; and switched back to tower (whose airspace was fairly close -- some ~8NM away -- to explain the mistaken identity and to ask if he was talking with the other [aircraft Y type]. The tower controller indicated that he was not talking with that aircraft but said he would relay the message if the [aircraft Y type] should check in.that was the end of the mistaken/unsafe condition and the rest of the flight proceeded normally.contributing factors to this confusion included:1) the remarkable coincidence that the mistaken [aircraft Y type] was in exactly the right place at the right time and the right altitude; and that it subsequently began a turn exactly when I requested my flight lead to do so2) my failure to ask my training partner to utilize TCAS/ads-B to firmly establish me on his pfd prior to my moving in on what I thought was the flight lead3) my electing to join from a trail position; which denied my flight lead a chance at a visual until later in the process4) my expectation bias that; because of corona; there would be few if any other aircraft and that this must have been my training partner (as it happens; the mistaken [aircraft Y type] and the intended [aircraft Y type] were the only two aircraft I saw or heard in the sky all day).
Original NASA ASRS Text
Title: GA pilot reported flying formation with the wrong aircraft. Reporter cited a number of contributing factors that led to this confusion.
Narrative: The objective for this particular flight was recurrent formation training for me; with the assistance of the pilot of a second aircraft (an occasional training partner; based at another nearby airport). Per our telephonic briefing on the ground; we agreed that we would rendezvous in a particular location and that he would fly lead and I would join off his wing there. We further agreed on a time; altitude; frequency and call signs.As I approached the practice area I observed at my 12 o'clock position at approximately 3;500 MSL an [Aircraft Y type] heading in the same direction -- i.e. to the center of the practice area.On the air-to-air frequency; I then made my first call to check in and to ask the flight lead if he was in position. He responded that he was approaching the practice area. I told him I thought I had him in sight.He then asked me my position; and I said I was at his 6 o'clock; several miles in trail. I told him he could maintain his heading and I would close from the rear.As I approached the [Aircraft Y type] in front of me; I suggested over the air-to-air frequency that my training partner make a shallow turn to help me close; and he acknowledged. A moment later; the [Aircraft Y type] in front of me began a gentle turn to the left.Once I was established in the turn and began to close; my partner asked for my current position; I indicated that I was moving from trail to his right wing. During this time I moved into a loose fingertip off the lead aircraft. About this time my partner asked again for my position and said he could not see me. I replied that I was off his right wing; and thought for a moment that possibly I was partly blocked by the window/door framing. To help with his field of view; I moved slightly forward to a more visible bearing line; and then radioed to ask if he had a clear visual. He responded that he still did not; and at that point it suddenly occurred to me that I might be flying formation off the wrong aircraft. Over the air-to-air frequency I read the N number of the [Aircraft Y type] in view; and asked if that was my training partner's aircraft (we had been using call signs; so I had not had any prior occasion to reference his N number). He replied that he was flying a different aircraft; and the mistaken identity suddenly was clear to us both.At the point; I broke off formation with the [Aircraft Y type]; and switched back to tower (whose airspace was fairly close -- some ~8NM away -- to explain the mistaken identity and to ask if he was talking with the other [Aircraft Y type]. The tower controller indicated that he was not talking with that aircraft but said he would relay the message if the [Aircraft Y type] should check in.That was the end of the mistaken/unsafe condition and the rest of the flight proceeded normally.Contributing factors to this confusion included:1) The remarkable coincidence that the mistaken [Aircraft Y type] was in exactly the right place at the right time and the right altitude; and that it subsequently began a turn exactly when I requested my flight lead to do so2) My failure to ask my training partner to utilize TCAS/ADS-B to firmly establish me on his PFD prior to my moving in on what I thought was the flight lead3) My electing to join from a trail position; which denied my flight lead a chance at a visual until later in the process4) My expectation bias that; because of Corona; there would be few if any other aircraft and that this must have been my training partner (as it happens; the mistaken [Aircraft Y type] and the intended [Aircraft Y type] were the only two aircraft I saw or heard in the sky all day).
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.