37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 913520 |
Time | |
Date | 201010 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | 1G3.Airport |
State Reference | OH |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Direct |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Flight Phase | Takeoff |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Air Traffic Control Fully Certified Flight Crew Private |
Experience | Flight Crew Last 90 Days 20 Flight Crew Total 250 Flight Crew Type 250 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 200 Vertical 200 |
Narrative:
Akron approach proceeded to let me change frequencies for I had 1g3 in sight. After changing the frequency in radio two to the kent frequency; I was using radio two for kent and listening to akron approach on radio one in case any planes might be in my area. This may be where the problem started for I was receiving both and transmitting on radio two. About this time I reported my position to be just north or akron near the cathedral buffet and will be entering an extended crosswind for 19. This was when I received a call from an airplane; which I latter learned was on takeoff from runway 19; they never said where they were they just asked me of my position. So transmitting on radio two I replied; 'just north of akron at 2;800 ft; entering an extended crosswind; downwind; base then final' in a sense giving them my full intentions. Then I got another radio call; which made me think it was the same people who asked for my location before; it was a plane doing an NDB1 into kent state on the 45 downwind for 19. Thus my full attention was trying to find the airplane in front of me and seeing that it was hazy I was looking hard. When I did see them I was just past the runway at what I thought was pattern altitude for I was trying to adjust the altimeter from the claims that cleveland center was giving me. After I saw the plane ahead of me I called back to the aircraft on the 45 that I saw him and I was above him and that I was ok. I can see now that this caused a confusion of position and who people where talking to; I was referring to the aircraft on the 45 not the aircraft on takeoff touch and go. I apologize in saying I had no idea that they were even there; my focus was finding the plane heading straight on and I did not see or realize there was two planes in the pattern. The plane on the NDB1 turned left and I turned left and climbed a little bit; never realizing there was a plane below me and never seeing them as they passed under me and towards the south. I proceed to land with no farther issues and never realized what I had done; though the aircraft that was on takeoff never tried to call me afterward while I was landing to tell me what I almost did; nobody mentioned anything to me on the ground once I landed. I apologize for what happened but I think this was an issue of mistaken identity; in which the aircraft on takeoff was thinking I was talking to them when I thought I was talking to the aircraft on the 45 downwind for 19.
Original NASA ASRS Text
Title: C172 pilot experiences a NMAC entering the traffic pattern on cross wind with an aircraft that had just departed. Poor radio procedures led to a misidentification and a failure to realize that there were two aircraft in the pattern.
Narrative: Akron Approach proceeded to let me change frequencies for I had 1G3 in sight. After changing the frequency in radio two to the Kent frequency; I was using radio two for Kent and listening to Akron Approach on radio one in case any planes might be in my area. This may be where the problem started for I was receiving both and transmitting on radio two. About this time I reported my position to be just north or Akron near the Cathedral Buffet and will be entering an extended crosswind for 19. This was when I received a call from an airplane; which I latter learned was on takeoff from Runway 19; they never said where they were they just asked me of my position. So transmitting on radio two I replied; 'Just north of Akron at 2;800 FT; entering an extended crosswind; downwind; base then final' in a sense giving them my full intentions. Then I got another radio call; which made me think it was the same people who asked for my location before; it was a plane doing an NDB1 into Kent State on the 45 downwind for 19. Thus my full attention was trying to find the airplane in front of me and seeing that it was hazy I was looking hard. When I did see them I was just past the runway at what I thought was pattern altitude for I was trying to adjust the altimeter from the claims that Cleveland Center was giving me. After I saw the plane ahead of me I called back to the aircraft on the 45 that I saw him and I was above him and that I was OK. I can see now that this caused a confusion of position and who people where talking to; I was referring to the aircraft on the 45 not the aircraft on takeoff touch and go. I apologize in saying I had no idea that they were even there; my focus was finding the plane heading straight on and I did not see or realize there was two planes in the pattern. The plane on the NDB1 turned left and I turned left and climbed a little bit; never realizing there was a plane below me and never seeing them as they passed under me and towards the south. I proceed to land with no farther issues and never realized what I had done; though the aircraft that was on takeoff never tried to call me afterward while I was landing to tell me what I almost did; nobody mentioned anything to me on the ground once I landed. I apologize for what happened but I think this was an issue of mistaken identity; in which the aircraft on takeoff was thinking I was talking to them when I thought I was talking to the aircraft on the 45 downwind for 19.
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.