37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1285950 |
Time | |
Date | 201508 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | BEC.Airport |
State Reference | KS |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Bonanza 36 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Person 1 | |
Function | Instructor Pilot Not Flying |
Qualification | Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 90 Flight Crew Total 2800 Flight Crew Type 190 |
Events | |
Anomaly | Conflict NMAC Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 500 Vertical 0 |
Narrative:
While on final approach to runway 1 at bec (beech factory airport); we executed a go-around at approximately 100 feet AGL because of another aircraft that was approaching on runway 19. The other aircraft executed a go-around at approximately the same time. Both aircraft side-stepped to their respective right; and both aircraft passed each other; opposite direction; with adequate separation. No CTAF calls were made by the other aircraft.postflight discussion with the crew of the other aircraft revealed that they were on the incorrect communication frequency. They'd forgotten to switch from the 3AU (augusta municipal airport) CTAF. (3AU is a nearby airport.) therefore; we did not hear each other's calls.light and variable winds prevailed throughout the evening. At the time of our arrival to bec; winds were reported 070 @ 6 KTS at aao (colonel james jabara airport). Aao is the nearest airport with an AWOS system. We selected runway 1 because the winds; although light; favored runway 1.contributing factors:1) winds were light and variable throughout the evening; which made runway selection ambiguous.2) improper communication frequency was used by the other aircraft.3) other aircraft was a checkride flight; so the PIC applicant was under pressure.4) both aircraft failed to see each other until on short final.good points:1) both aircraft executed proper go-arounds; which ensured adequate separation.2) both aircraft had landing lights on; which enhanced aircraft visibility.
Original NASA ASRS Text
Title: C172 instructor pilot reported executing a go around on approach to BEC Runway 1 when he noticed another aircraft on approach to Runway 19 who was not on CTAF frequency.
Narrative: While on final approach to Runway 1 at BEC (Beech Factory Airport); we executed a go-around at approximately 100 feet AGL because of another aircraft that was approaching on Runway 19. The other aircraft executed a go-around at approximately the same time. Both aircraft side-stepped to their respective right; and both aircraft passed each other; opposite direction; with adequate separation. No CTAF calls were made by the other aircraft.Postflight discussion with the crew of the other aircraft revealed that they were on the incorrect communication frequency. They'd forgotten to switch from the 3AU (Augusta Municipal Airport) CTAF. (3AU is a nearby airport.) Therefore; we did not hear each other's calls.Light and variable winds prevailed throughout the evening. At the time of our arrival to BEC; winds were reported 070 @ 6 KTS at AAO (Colonel James Jabara Airport). AAO is the nearest airport with an AWOS system. We selected Runway 1 because the winds; although light; favored Runway 1.Contributing factors:1) Winds were light and variable throughout the evening; which made runway selection ambiguous.2) Improper communication frequency was used by the other aircraft.3) Other aircraft was a checkride flight; so the PIC applicant was under pressure.4) Both aircraft failed to see each other until on short final.Good points:1) Both aircraft executed proper go-arounds; which ensured adequate separation.2) Both aircraft had landing lights on; which enhanced aircraft visibility.
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.