37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1341262 |
Time | |
Date | 201603 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Flight Instructor Flight Crew Flight Engineer Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 154 Flight Crew Total 9000 Flight Crew Type 500 |
Person 2 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 75 Flight Crew Total 4506 Flight Crew Type 110 |
Events | |
Anomaly | Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy Ground Event / Encounter Aircraft |
Narrative:
Enroute to udd I checked the weather via internet to determine the conditions in the palm springs area. The closest airport with weather reporting was trm and it was showing 'clear skies with light and variable winds'. I then briefed a landing on runway 10 as it was the preferred runway due to its extra length. When we got closer the first officer (first officer) was able to receive the trm ASOS and confirmed that weather was as previously reported. Approximately 20 miles from the airport; we cancelled IFR with socal approach and proceeded visually towards the airport. We also both began monitoring the unicom frequency and the first officer began making position reports stating our intentions to land on runway 10. At about 8 miles from the airport we heard [another] jet call us to tell us they would be holding short of the runway on the last taxiway at the end of the runway. I briefed the fact that we would turn off the runway before the last taxiway to avoid a 180 turn on the narrow runway. No other aircraft radio calls were heard on unicom and the first officer continued position reports as we got closer. The landing checklist was completed and the aircraft was fully configured in a stabilized approach with all required lights on. This was to be a strictly visual approach and my eyes were focused on the spot on the runway where I intended to touch down. As I was starting to flare and pull the thrust levers back to idle the first officer urgently warned about an aircraft on the runway. I took me a moment to realize what he had said and I looked further down the runway and saw a small single engine airplane coming towards us. I immediately initiated a go around maneuver and we began climbing straight-ahead back up to traffic pattern altitude. At 1;600 feet I reentered the left traffic pattern for runway 10. At about that time we heard radio communications stating that an airplane was off the runway. I decided to continue around the pattern and we were able to see that a single engine plane was off in the grass next to the runway. Shortly thereafter; we heard a unicom call stating that the airport was now closed. I continued to fly the pattern around udd as we discussed our next course of action. I anticipated that the airport would be closed for a substantial period of time. After consulting with our passengers; we decided to divert to trm. We were in the process of configuring and briefing for the diversion to trm when we heard on unicom that the airport was open again. We saw that runway 10/28 was now clear. I again briefed our passengers and told them that we would be landing at udd. We were in the left downwind for runway 28 and I elected to make an extended downwind and use 28. We saw the falcon jet still holding on the taxiway short of the runway at the beginning of 28. We landed and taxied to the terminal. After assisting our passengers; we talked with several airport employees and other pilots who stated that they had never heard the single engine aircraft make any radio calls. As we were shutting down the aircraft two udd airport managers came over to talk to us. We found out that the single engine airplane had just landed and then swerved into the grass to get out of our way. It was then pulled out of the grass right away. They stated the pilot was probably either transmitting on the wrong frequency or had an inoperative radio.
Original NASA ASRS Text
Title: Flight crew reported executing a go-around from a low altitude at UDD after spotting a light aircraft that had just landed on the opposite direction runway without any radio contact.
Narrative: Enroute to UDD I checked the weather via internet to determine the conditions in the Palm Springs area. The closest airport with weather reporting was TRM and it was showing 'clear skies with light and variable winds'. I then briefed a landing on Runway 10 as it was the preferred runway due to its extra length. When we got closer the First Officer (FO) was able to receive the TRM ASOS and confirmed that weather was as previously reported. Approximately 20 miles from the airport; we cancelled IFR with SOCAL Approach and proceeded visually towards the airport. We also both began monitoring the UNICOM frequency and the FO began making position reports stating our intentions to land on Runway 10. At about 8 miles from the airport we heard [another] jet call us to tell us they would be holding short of the runway on the last taxiway at the end of the runway. I briefed the fact that we would turn off the runway before the last taxiway to avoid a 180 turn on the narrow runway. No other aircraft radio calls were heard on UNICOM and the FO continued position reports as we got closer. The Landing Checklist was completed and the aircraft was fully configured in a stabilized approach with all required lights on. This was to be a strictly visual approach and my eyes were focused on the spot on the runway where I intended to touch down. As I was starting to flare and pull the thrust levers back to idle the FO urgently warned about an aircraft on the runway. I took me a moment to realize what he had said and I looked further down the runway and saw a small single engine airplane coming towards us. I immediately initiated a Go Around maneuver and we began climbing straight-ahead back up to traffic pattern altitude. At 1;600 feet I reentered the left traffic pattern for Runway 10. At about that time we heard radio communications stating that an airplane was off the runway. I decided to continue around the pattern and we were able to see that a single engine plane was off in the grass next to the runway. Shortly thereafter; we heard a UNICOM call stating that the airport was now closed. I continued to fly the pattern around UDD as we discussed our next course of action. I anticipated that the airport would be closed for a substantial period of time. After consulting with our passengers; we decided to divert to TRM. We were in the process of configuring and briefing for the diversion to TRM when we heard on UNICOM that the airport was open again. We saw that runway 10/28 was now clear. I again briefed our passengers and told them that we would be landing at UDD. We were in the left downwind for runway 28 and I elected to make an extended downwind and use 28. We saw the Falcon jet still holding on the taxiway short of the runway at the beginning of 28. We landed and taxied to the terminal. After assisting our passengers; we talked with several airport employees and other pilots who stated that they had never heard the single engine aircraft make any radio calls. As we were shutting down the aircraft two UDD airport managers came over to talk to us. We found out that the single engine airplane had just landed and then swerved into the grass to get out of our way. It was then pulled out of the grass right away. They stated the pilot was probably either transmitting on the wrong frequency or had an inoperative radio.
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.