37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 895542 |
Time | |
Date | 201006 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | N12.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | None |
Person 1 | |
Function | Instructor |
Qualification | Flight Crew Flight Instructor Flight Crew Commercial Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 70 Flight Crew Total 560 Flight Crew Type 100 |
Narrative:
[I was in a] local area training flight with private pilot student. [We] performed three previous landings at lakewood airport; N12; to a full stop. CTAF frequency is 122.8; multiple other pilots operating on this station. FAA publications show 122.8 as correct frequency. On approach number four; a short field landing; we were rolling out from our base to final turn at approximately 500 ft MSL. All radio calls were performed as normal. At this time; I saw a shimmering in the corner of my right eye. I glanced over to see a high winged aircraft just a few feet below the right main gear. I took the controls from the student and immediately climbed to the left; going around and aborting the landing. We circled back to land behind the [other aircraft]. On our approach back down; I tried to raise the conflicting aircraft on the radio; but to no avail. My student and I parked the aircraft on the ground so we could settle down for a few minutes. On the ground we were parked next to the offending pilot. I asked him if he knew what happened on final. He had no idea; as expected; since his wing blocked us from view. I asked if he was on the radio making position reports; and he said yes; on 122.7. This frequency is not correct; it is 122.8 for lakewood. He countered by showing me a print out from AOPA with an airport diagram and CTAF numbers where it did indeed say 122.7. Additionally; he said he entered the pattern on a right base; 360 degree descending turn to final. This airport operates with a left hand traffic pattern for this runway. Further research post-flight shows that the aircraft partially received flight following services to toms river; nj at the mjx airport; 10 miles south of N12. The runway numbers are the same; 6/24. Also; the frequency for mjx is 122.7. All FAA charts; and current AOPA charts; show 122.8 for N12 and 122.7 for mjx. Taking all of this into consideration; I believe this pilot landed at the wrong airport; believing he was on the proper frequency; and ignored the standard and published left hand traffic turns for both runway 6s at both airports. During our base to final turn; we routinely clear the entire area before we turn. However; his right hand descending 360 likely put him out of sight during our turn. Corrective actions on our part would be to more thoroughly find a way to scan the entire traffic area; or to install an external traffic system. There are only so many measures a pilot can make to ensure he is being safe. When other pilots blatantly ignore standard procedure; all of this effort is defeated.
Original NASA ASRS Text
Title: A light aircraft instructor pilot reported an NMAC with another light aircraft at N12. It appears likely the other aircraft landed at the wrong airport and therefore was using incorrect frequencies and procedures.
Narrative: [I was in a] local area training flight with Private Pilot Student. [We] performed three previous landings at Lakewood Airport; N12; to a full stop. CTAF frequency is 122.8; multiple other pilots operating on this station. FAA Publications show 122.8 as correct frequency. On approach number four; a short field landing; we were rolling out from our base to final turn at approximately 500 FT MSL. All radio calls were performed as normal. At this time; I saw a shimmering in the corner of my right eye. I glanced over to see a high winged aircraft just a few feet below the right main gear. I took the controls from the student and immediately climbed to the left; going around and aborting the landing. We circled back to land behind the [other aircraft]. On our approach back down; I tried to raise the conflicting aircraft on the radio; but to no avail. My student and I parked the aircraft on the ground so we could settle down for a few minutes. On the ground we were parked next to the offending pilot. I asked him if he knew what happened on final. He had no idea; as expected; since his wing blocked us from view. I asked if he was on the radio making position reports; and he said yes; on 122.7. This frequency is not correct; it is 122.8 for Lakewood. He countered by showing me a print out from AOPA with an airport diagram and CTAF numbers where it did indeed say 122.7. Additionally; he said he entered the pattern on a right base; 360 degree descending turn to final. This airport operates with a left hand traffic pattern for this runway. Further research post-flight shows that the aircraft partially received flight following services to Toms River; NJ at the MJX airport; 10 miles south of N12. The runway numbers are the same; 6/24. Also; the frequency for MJX is 122.7. All FAA charts; and current AOPA charts; show 122.8 for N12 and 122.7 for MJX. Taking all of this into consideration; I believe this pilot landed at the wrong airport; believing he was on the proper frequency; and ignored the standard and published left hand traffic turns for both Runway 6s at both airports. During our base to final turn; we routinely clear the entire area before we turn. However; his right hand descending 360 likely put him out of sight during our turn. Corrective actions on our part would be to more thoroughly find a way to scan the entire traffic area; or to install an external traffic system. There are only so many measures a pilot can make to ensure he is being safe. When other pilots blatantly ignore standard procedure; all of this effort is defeated.
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.