2011-12 · NASA ASRS report 983029
A CE680 left landing gear did not indicate down on approach. A missed approach was executed; but the crew climbed to 3;000 FT with an initial level off altitude of 2;500 FT and caused a conflict with a nearby airport's inbound traffic.
During the ILS approach; the left landing gear did not indicate down and locked. After cycling the gear there was still no indication. Tower was informed that we would need to break off the approach due to a landing gear issue. I initiated a go-around and asked the pilot not flying to verify the initial altitude on the missed approach procedure. The initial altitude is 1;500 FT; so I began a climb to 1;500 FT and shortly after was advised by Tower to fly runway heading at 1;000 FT. After establishing 1;000 FT on the runway heading we were given the clearance to fly the published missed. At the time we were given this clearance; we had flown down the runway and were now south of the missed approach point for the published missed. I selected long range navigation and ensured that the FMS had sequenced to the missed approach procedure when I had hit the TOGO button. The FMS was selected to the first fix and I continued to hand fly the aircraft using the flight director for guidance. When given the published missed I asked the pilot not flying what the altitude was for the missed and we set 3;000 FT in the altitude select. Since we were south of the airport now a right turn to the north/northeast was required to get back on course. During the flight to re-establish the proper course for the published procedure we were told to make an immediate descent to 2;000 FT; at which time I complied and also realized that we were only to be at 1;500 FT until the first fix and then up to 3;000 FT after it. After the descent to 2;000 FT the TRACON began giving vectors and we received two traffic advisories from the TRACON. We were in VMC and were ably to visually make contact with the aircraft. There was 1;000 FT vertical separation and no TCAS alerts sounded. Upon being able to investigate the landing gear issue; we discovered that one of the bulbs was inoperative in the left gear down indicator and the other bulb began to work when pushed. The one light bulb continued to work for the remainder of the flight. A second ILS was performed with no issues and I was told to call the TRACON. I called and was advised to call the Manager of Quality Assurance in the morning since I had caused a 'loss of separation.' I spoke with my Chief Pilot after these conversations to alert the Company of the incident. I called the next morning and was advised by the Quality Assurance Manager that a report is automatically generated and sent to the Regional FSDO and then sent on to the overseeing FSDO of the operator. Obviously equipment malfunctions cause a distraction in the cockpit which adds to the workload and complicates matters. Receiving a clearance that is not expected and then having it changed after flying passed the missed approach point complicates matters further. In the event of a missed approach with a possible equipment malfunction it is best to state that one is going missed and will perform the published missed. If given something different by the Tower; the Tower should be able to give vectors and altitude guidance away from the traffic area. In our case we were expecting to land in VMC conditions and had not planned to go-around. When the situation developed to a go-around we expected the published missed. When not given the published missed; we expected vectors; but was then put back on the published missed after flying well beyond the missed approach point. We were required to make unplanned turns back to the missed approach course and during the confusion and distraction of a gear malfunction failed to set the proper altitude in the altitude select. Had we flown the published missed from the beginning; we would have been on course in a safe area that the altitude deviation would not have caused a 'loss of separation' at TRACON. Unfortunately; the Tower gave us runway heading long enough that we had to turn through the course of arrivals to get back on the published missed. In the end what seems to be best is to always plan for a missed approach even in VMC conditions and always plan to do the published missed. When calling Tower to go around; state that the published missed will be flown and require ATC to provide heading and altitude guidance if they require anything other than the published missed.
This occurrence was effected by many factors. With the weather conditions being VMC at the arrival time; a completed approach to landing is almost a guarantee. Having a gear malfunction on short final; causing stress and distraction in the cockpit; then having alternate missed approach instructions; followed by a change back to the original missed approach instructions compounded the stress level to the crew. This event could have been avoided had we just asked for the published missed approach initially or requested alternate instructions from the Controller.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.