Most Puckered Instrument Approach

Subscribe
1  2  3  4  5  6  7  8 
Page 4 of 8
Go to
Quote: actually,100 feet above,it worked out better than i had hoped,wx was reported right at minnies,and we didn't pick up any ice on the approach,though the freezing rain moved in after we landed and our boys up north had to wait 2 days before they could fly in and rescue/fix us.God is good to us !!!

Good answer. I always laugh on one of those days when it is just pure soup out and tower asks "what did you break out at" there is always a pause on the radio (while PF & PNF are consulting each other for the best answer) and the answer always heard on the radio is "right at minimums"!!!


Swear to God I heard someone once say "below minimums" with a quick comeback in a different voice "at minimums"
Reply
Quote: Carrier landing, first cruise, but a reverse. Had only flown Case III instrument approaches (equivalent of straight in ILS, talk on radios) all cruise, somehow Skipper liked me flying nights or crappy wx day flying only. 5 months into cruise, had the scariest approach.
The setup? day time, clear and a million, calm sea state, regular overhead, oval pattern approach, over the boat, a standard Case I Zip Lip (no radios)

Holy crap! Realized I hadn't flown a visual approach to mom (boat) and was screwing up everything with a pattern full of birds! the interval, the distance abeam, groove length...... Intense pucker factor, was glad to get back to night carrier, no moon, instrument approach straight in landings for the short time left on cruise after that sweat dripping approach <g>
My nugget cruise we spent the better part of 3-4 months running night ops out of the NAG in OIF. It was pretty much an airwing wide joke that no one wanted to fly the day Case I pattern because no one knew how to find a good start anymore. Made for some hilarious platcam hijinks when we'd have a day off the night page for some "good deal" day flying.
Reply
Quote: My nugget cruise we spent the better part of 3-4 months running night ops out of the NAG in OIF. It was pretty much an airwing wide joke that no one wanted to fly the day Case I pattern because no one knew how to find a good start anymore. Made for some hilarious platcam hijinks when we'd have a day off the night page for some "good deal" day flying.
Haha...It's like you're speaking a foreign language Grumble!
Reply
Quote: My nugget cruise we spent the better part of 3-4 months running night ops out of the NAG in OIF. It was pretty much an airwing wide joke that no one wanted to fly the day Case I pattern because no one knew how to find a good start anymore. Made for some hilarious platcam hijinks when we'd have a day off the night page for some "good deal" day flying.
Quote: Haha...It's like you're speaking a foreign language Grumble!
Come on crewdawg!
Just apply that same language interpetation programming that we (the naval services) have to use every time an AF guy gives us a "cranium's up" that they are getting ready to "step to the aircraft".
It is all good

USMCFLYR
Reply
Crewdog:
Box box box, head, box box, head head head

USMC:
Yut yut, ooh rah, devil dog

Everyone should be on the same page.
Reply
Quote: Come on crewdawg!
Just apply that same language interpetation programming that we (the naval services) have to use every time an AF guy gives us a "cranium's up" that they are getting ready to "step to the aircraft".
It is all good

USMCFLYR
Quote: Crewdog:
Box box box, head, box box, head head head

USMC:
Yut yut, ooh rah, devil dog

Everyone should be on the same page.
Haha...good stuff guys. I'm going to have to spend some more time on Airwarriors...Or more TDY's for some dissimilar!
Reply
MD-11 flight from Indianapolis to Anchorage. I was Memphis based and my F/O was Anchorage based. The jet had the #2 bleed air valve wired open (for some reason that I cannot remember at this time) On climbout, at about FL250, the aircraft announced a #2 Bleed Air Manifold Failure, followed shortly by a #2 Bleed Air High Temperature warning. After consulting the checklists, which didn't offer much guidance, I decided to shut down the number 2 engine, because we had no way of stopping the flow of super-heated air into the manifold.

We were over Chicago, when my F/O said: “I think we can still make Anchorage.” I’ve heard of get-home-itis before, but this was ridiculous. I mentioned that I’d like to keep my job for a little while longer, and because of that, we were going to land somewhere close. I asked him for wx at ORD as well as IND and MEM, to help us decide where we were going to set this puppy down. It was about 0830L in ORD and when the wx for IND came back as CAVU, I decided that we’d return to there, not wanting to disrupt the takeoff patterns at ORD, and we had to dump 50,000 of gas to get down to max landing weight anyway.

All was going to plan, when about 15 miles from the FAF, approach control mentioned that the weather had gone from clear to RVR’s. He then reported that the RVR’s for RW05R were 6/4/6. We still had plenty of fuel, so I asked for holding, and I mentioned to approach control that we needed 6/6/6 before we could begin the approach. As we were entering holding, app. Con. Issued a new wx report (surprise, surprise), RVR’s were now (magically 6/6/6), but not on 05R, only on 05L. The F/O was flying so I entered the new approach in the box and away we went. I had briefed an engine out CATIIIB, under captains emergency authority.

Everything worked as planned, except we never broke out. By that, I mean that the first time I saw any part of the earth, was when the nose wheel touched down. Thankfully everything worked as advertised and the jet tracked the centerline perfectly. I disconnected the autoflight at about 10 knots, and followed a turnoff line off the runway. From there it took us almost 40 minutes to taxi to our ramp. There was absolutely no visibility at all and the MD-11 has to oversteer on 90 degree turns to keep it on the taxiway. I was concerned that I'd not see the damn lines on the way back to centerline. Anyway, FedEx has a huge ramp in Indy, and when we finally turned off the taxiway and into our ramp area, we had to have a followme come out and lead us to our gate. Everything happened at about a half-mile an hour, and when we finally made it to the lead-in line, I continued ahead until the last second, when I finally saw the marshaller, who was on a ramp tower, lit wands in hand, signaling me. I don’t think he was 10 feet ahead of us when we finally saw him. After shutdown, the marshaller came up to the cockpit and said that he didn’t see us until the very last second and that he was thinking of jumping off the tower, because he didn’t know if we could stop in time to not hit him and then the building.

I know it's not a night trap, but I gotta tell you, that was the scariest approach/landing/taxi-in, by far, in my entire career. And of course, my first officer was annoyed that he didn't get home that night.

JJ
Reply
Took off from Chicago Dupage on a night freight run to Chicago Midway. Wx was 500 and 2ish. Departing east for a very short flight, rwy 10 to vectors for rwy 13. After departure started the right turn to the assigned heading. The ADI showed a right turn but the HSI didn't move. Let me tell you, you have not experienced partial panel, until you've experienced partial panel. Looked across the cockpit to the DG and determined that was working.

On the approach to MDW, found that both LOC receivers were in disagreement. Flew the ILS by splitting the LOC receivers and going cross cockpit for heading. Sure was glad to see those approach lights. I was 22 and stupid... So I finished the run to MKE and back with that airplane.

"Good judgment comes from experience, experience comes from bad judgment"
Reply
Quote: My nugget cruise we spent the better part of 3-4 months running night ops out of the NAG in OIF. It was pretty much an airwing wide joke that no one wanted to fly the day Case I pattern because no one knew how to find a good start anymore.
Reminds me of the time our air wing tried to do the CV-2 (?) teardrop approach. We butchered it so bad that the first plane hadn't made it to final before CATCC gave up and just assigned everyone vectors.
Reply
Quote: We still had plenty of fuel, so I asked for holding, and I mentioned to approach control that we needed 6/6/6 before we could begin the approach. As we were entering holding, app. Con. Issued a new wx report (surprise, surprise), RVR’s were now (magically 6/6/6), but not on 05R, only on 05L.
I was told the 600 RVR is actually for ground ops like taxiing and crash & rescue. Below that it takes too long for them to find the wreckage.
Reply
1  2  3  4  5  6  7  8 
Page 4 of 8
Go to