37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1346178 |
Time | |
Date | 201604 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 90 Flight Crew Total 5200 Flight Crew Type 550 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
Aircraft with passengers to land on a 5;000 foot runway. Pattern saturated with 5 small aircraft flying orientation flights for students and one airborne aircraft with jumpers: no control tower. We were on vectors to do an RNAV approach to runway 31 talking with ATC on IFR clearance. Trying to monitor unicom and talk to ATC at the same time became complicated so we told ATC we would cancel on the ground and received a phone number from them.small aircraft pilots reported gusty winds with wind shear on final. Pilot flying executed a go around in the flare for a wind shear; and subsequent climb out was on unicom. About that time the jump aircraft reported jumpers in the air so we began to coordinate with them on unicom and climbed to a VFR altitude and flew back to the 10 mile point to avoid jumpers. In the rapidly changing situation with the winds; other aircraft and jumpers we spent the time coordinating with them on unicom rather than contacting ATC again and executing the published missed approach. Honestly; we were so busy we just didn't think about it as we should have. In retrospect we should have just cancelled in the air and ATC would have been relieved of the responsibility of us; but we didn't. When we called to cancel; they advised us to call another number to discuss our not contacting them.the winds; extreme unusual pattern activity; and a balked landing all contributed to additional tasking in the cockpit leading to safety focus first allowing the IFR regulation to contact approach control lapse.
Original NASA ASRS Text
Title: Corporate jet with passengers attempted a landing at an uncontrolled airport with heavy traffic in the pattern. Additionally; windshear conditions existed prompting a go-around. Because of the heavy workload there was a lapse in the coordination with ATC.
Narrative: Aircraft with passengers to land on a 5;000 foot runway. Pattern saturated with 5 small aircraft flying orientation flights for students and one airborne aircraft with jumpers: no control tower. We were on vectors to do an RNAV approach to Runway 31 talking with ATC on IFR clearance. Trying to monitor UNICOM and talk to ATC at the same time became complicated so we told ATC we would cancel on the ground and received a phone number from them.Small aircraft pilots reported gusty winds with wind shear on final. Pilot flying executed a go around in the flare for a wind shear; and subsequent climb out was on UNICOM. About that time the jump aircraft reported jumpers in the air so we began to coordinate with them on UNICOM and climbed to a VFR altitude and flew back to the 10 mile point to avoid jumpers. In the rapidly changing situation with the winds; other aircraft and jumpers we spent the time coordinating with them on UNICOM rather than contacting ATC again and executing the published missed approach. Honestly; we were so busy we just didn't think about it as we should have. In retrospect we should have just cancelled in the air and ATC would have been relieved of the responsibility of us; but we didn't. When we called to cancel; they advised us to call another number to discuss our not contacting them.The winds; extreme unusual pattern activity; and a balked landing all contributed to additional tasking in the cockpit leading to safety focus first allowing the IFR regulation to contact approach control lapse.
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.