B737-500 CAPT RPTS DIFFICULTY RETRACTING LNDG GEAR AFTER TKOF. QRH PROC FAILS TO DIRECT CREW TO CHK CIRCUIT BREAKER THAT IF CHKED MIGHT SOLVE THE PROB.

2007-03 · NASA ASRS report 731570

Date: 2007-03 · Aircraft: B737-500 · Phase: initial_climb

Anomalies: aircraft-equipment-problem-critical|other-qrh-procedure

Synopsis

B737-500 CAPT RPTS DIFFICULTY RETRACTING LNDG GEAR AFTER TKOF. QRH PROC FAILS TO DIRECT CREW TO CHK CIRCUIT BREAKER THAT IF CHKED MIGHT SOLVE THE PROB.

Narrative

AS THE PF; I MADE THE TAKEOFF. AT A POSITIVE RATE OF CLIMB; I COMMANDED; 'LANDING GEAR UP.' THE FO MOVED THE GEAR LEVER TO THE NEUTRAL POSITION ONLY AND SAID HE WAS HAVING TROUBLE GETTING THE GEAR UP. I GLANCED OVER AND SAW 3 RED AND 3 GREEN LANDING GEAR LIGHTS. ABOUT THE SAME TIME HE MOVED THE GEAR HANDLE TO THE UP POSITION AND THE GEAR RETRACTED NORMALLY. HE STATED THAT HE HAD HAD TO PULL THE LANDING GEAR LEVER OVERRIDE TRIGGER TO GET THE GEAR HANDLE UP. SINCE ALL INDICATIONS WERE NORMAL AT THIS POINT AND IT WAS A VERY BUSY/DYNAMIC PHASE OF FLIGHT; I DECIDED TO CONTINUE TO FLY A NORMAL DEPARTURE AND GET AWAY FROM THE BUSY AIRPORT TRAFFIC AREA BEFORE WE REFERENCED THE QRH. THE FO THEN REVIEWED THE APPROPRIATE CHECKLIST ON PAGE X-X OF THE QRH; NOTED THAT IT WAS COMPLETE AND ADVISED THAT IT DIRECTED CONTACT WITH DISPATCH ABOUT A POSSIBLE RETURN TO ZZZ. CONTROL OF THE ACFT WAS TRANSFERRED WHILE I REVIEWED THE QRH MYSELF. WE DID INITIATE A RADIO PATCH WITH DISPATCH AND ADVISED THEM OF OUR NON-NORMAL LANDING GEAR RETRACTION. WE ASKED THAT THEY CONTACT MAINTENANCE FOR ANY POSSIBLE IDEAS OR SUGGESTIONS. MX ASKED THAT WE CYCLE THE GEAR AGAIN TO SEE IF THE GEAR REQUIRED ANOTHER OVERRIDE TO RETRACT. THIS WAS DONE AND ONCE AGAIN; THE GEAR DID NOT RETRACT NORMALLY. AT THAT POINT DISPATCH DIRECTED US TO RETURN TO ZZZ AT THE REQUEST OF MX CONTROL. WE INITIATED A RETURN TO ZZZ. AFTER WE HAD COMMITTED TO THE RETURN; WE FOUND THAT THE LG LATCH AND PRESS WARN CIRCUIT BREAKER WAS OUT. SINCE THE RETURN FLIGHT HAD BEEN INITIATED AND WE WEREN'T CERTAIN OF THE CAUSE OF THE POPPED CIRCUIT BREAKER; WE WENT AHEAD WITH AN UNEVENTFUL ARRIVAL AND LANDING IN ZZZ. AN APPROPRIATE LOGBOOK ENTRY WAS MADE WITH THE ABOVE FACTS. I THINK THAT ANY QRH ITEM THAT MAY HAVE BEEN CAUSED BY A TRIPPED CIRCUIT BREAKER SHOULD DIRECT YOU TO CHECK THAT SPECIFIC CIRCUIT BREAKER.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.