37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1562602 |
Time | |
Date | 201807 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Route In Use | VFR Route |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Small Transport |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Person 1 | |
Function | Captain |
Events | |
Anomaly | Conflict Ground Conflict Critical Conflict NMAC Deviation - Procedural Published Material / Policy |
Narrative:
Our flight departed enroute to ZZZ on a beautiful clear day with a filed VFR flight plan with FSS. We entered a modified 10 mile final to runway with less than 5 knots of wind. We called CTAF with a 10 mile final call; 5 mile final; and short final call. After the short final call a gentleman from the airport operations called and said a medevac aircraft operated was rolling opposite of us on runway 28. We couldn't see the aircraft until he rotated with his lights on. There was absolutely no communication from that aircraft on CTAF. On short final (along with a TCAS alert) we executed a missed approach and flew to the right of centerline to avoid the aircraft. The maneuvering capability is somewhat limited in a 737 with those mountains in the airport area but I knew per the 10-7 and prior knowledge that I could keep a 30 degree bank to the left and reenter a base/final and land again on runway 10 which is the preferred runway for us. Even on a clear day an aircraft [like that] is tough to see when lined up on the centerline and taking off without a communication to others. Without the help of airport operations and a preempted missed approach by us; this could have been a disastrous situation. I called FSS and reported that an aircraft didn't make any radio calls and was putting others at risk. FSS said that happens on occasion and left it at that. The aircraft was going to ZZZ 1. There needs to be some accountability towards aircraft that don't communicate on CTAF especially in this state. This has happened more than once and will continue unless another option is used. I get that they need to depart as soon as possible and usually get priority but safety is paramount in situations like this. I think FSS could have been more helpful to both aircraft and could have communicated to the other aircraft that there was a 737 that was due in at that time as well as we just filed less than 30 minutes earlier and fly the exact same route daily. Finally I think that ZZZ airport manager should get a safety award for his alertness of the airport area.
Original NASA ASRS Text
Title: B737 Captain reported taking evasive action to avoid another aircraft departing in their direction.
Narrative: Our flight departed enroute to ZZZ on a beautiful clear day with a filed VFR flight plan with FSS. We entered a modified 10 mile final to runway with less than 5 knots of wind. We called CTAF with a 10 mile final call; 5 mile final; and short final call. After the short final call a gentleman from the airport operations called and said a medevac aircraft operated was rolling opposite of us on Runway 28. We couldn't see the aircraft until he rotated with his lights on. THERE WAS ABSOLUTELY NO COMMUNICATION FROM THAT AIRCRAFT ON CTAF. On short final (along with a TCAS ALERT) we executed a missed approach and flew to the right of centerline to avoid the aircraft. The maneuvering capability is somewhat limited in a 737 with those mountains in the airport area but I knew per the 10-7 and prior knowledge that I could keep a 30 degree bank to the left and reenter a base/final and land again on Runway 10 which is the preferred runway for us. Even on a clear day an aircraft [like that] is tough to see when lined up on the centerline and taking off without a communication to others. Without the help of airport operations and a preempted missed approach by us; this could have been a disastrous situation. I called FSS and reported that an aircraft didn't make any radio calls and was putting others at risk. FSS said that happens on occasion and left it at that. The aircraft was going to ZZZ 1. There needs to be some accountability towards aircraft that don't communicate on CTAF especially in this state. This has happened more than once and will continue unless another option is used. I get that they need to depart ASAP and usually get priority but safety is paramount in situations like this. I think FSS could have been more helpful to both aircraft and could have communicated to the other aircraft that there was a 737 that was due in at that time as well as we just filed less than 30 minutes earlier and fly the exact same route daily. Finally I think that ZZZ airport manager should get a safety award for his alertness of the airport area.
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.