37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1089069 |
Time | |
Date | 201305 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | CBE.Airport |
State Reference | MD |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
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 |
Aircraft 2 | |
Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Private Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 2.7 Flight Crew Total 365 Flight Crew Type 250 |
Events | |
Anomaly | Conflict NMAC Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 150 Vertical 200 |
Narrative:
Practicing landings (touch 'n goes) I was on a long final (due to practicing no-flaps approach and landing) to runway 23 at cbe. I was about 1/3 to 1/2 mile from runway threshold and about 150 feet right of extended centerline. I happened to see an aircraft (I believe a small cessna) about 200 feet below me and about 150 feet to my left.I initiated a go-around; and announced I was going around on unicom. Someone (presumably the pilot of that aircraft) said 'sorry about that - I was on the wrong frequency'; or something very close to that. I replied something to the effect of 'no problem; no one got hurt'.I did a couple more landings after the incident and put the aircraft away. I did not see the other aircraft or pilot.at no time did I hear the pilot of that aircraft on the radio; except immediately after I announced that I was going around. I do not know if he had flown a partial or complete pattern or did a straight-in approach.preventive action to try to prevent this from happening again: 1) try to improve my scan for other aircraft. I was looking for other aircraft; but just did not see him.2) make sure I am on correct frequency; monitor radio traffic to build situational awareness; and clearly announce my position/intentions as we're supposed to do.
Original NASA ASRS Text
Title: A pilot on short final to CTAF CBE Runway 23 executed a go-around after a near miss with an aircraft whose pilot failed to employ recommended CTAF communications reporting.
Narrative: Practicing landings (touch 'n goes) I was on a long final (due to practicing no-flaps approach and landing) to Runway 23 at CBE. I was about 1/3 to 1/2 mile from runway threshold and about 150 feet right of extended centerline. I happened to see an aircraft (I believe a small Cessna) about 200 feet below me and about 150 feet to my left.I initiated a go-around; and announced I was going around on UNICOM. Someone (presumably the pilot of that aircraft) said 'sorry about that - I was on the wrong frequency'; or something very close to that. I replied something to the effect of 'no problem; no one got hurt'.I did a couple more landings after the incident and put the aircraft away. I did not see the other aircraft or pilot.At no time did I hear the pilot of that aircraft on the radio; except immediately after I announced that I was going around. I do not know if he had flown a partial or complete pattern or did a straight-in approach.Preventive action to try to prevent this from happening again: 1) try to improve my scan for other aircraft. I was looking for other aircraft; but just did not see him.2) make sure I am on correct frequency; monitor radio traffic to build situational awareness; and clearly announce my position/intentions as we're supposed to do.
Data retrieved from NASA's ASRS site as of July 2013 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.