![]() |
http://s2.quickmeme.com/img/68/68902...847c51596a.jpg
FLY THE AIRPLANE! There are more important things to worry about. |
Originally Posted by v1rotate88
(Post 1947992)
agreed, but there are some guys that live in sim land that are 65+,and haven't flown the line in 20 years. They definitely don't understand that reasoning sometimes.
|
Originally Posted by Slim11
(Post 1948040)
Many years ago, a Comair crew was violated at KLGA for this scenario. The ATIS stated the approach in use was the LDA-A landing Runway 22. The crew in question briefed the LDA-A and loaded it into the FMS. Approach asked them if they had the runway in sight and they confirmed Runway 22 was in sight. They were cleared for the visual approach for 22.
For some reason, they had to execute a go-around and started to fly the published MAP. They were asked where they were going and replied flying the published MAP. According to what was reported, they were expected to fly a closed traffic pattern to 1,500 feet AGL since they were cleared for a visual approach. I agree that tower facilities will usually give heading and altitude (ATL and CVG come to mind) to an airplane executing a go-around and many times it's not to an altitude that is 1,500 feet AGL. Sometimes, you ask tower for altitude and heading and they can't answer immediately (LGA and PHF come to mind)...what do you do then? Now, think about CLT and a visual approach to 18-36C. Do you make a LT across 36L interfering with arrivals or a RT interfering with arriving and departing traffic on 36R? I think ORD has a good idea in this scenario. On ATIS, they publish the ILS for the center runway and visuals of the L-/R-side runways. That tells me ATC expects arrivals to the center runways to fly a published MAP and arrivals to the outside runways to execute a visual go-around. When a visual approach has been briefed, sometimes a pilot will put in the FAF crossing altitude for the go-around altitude. IMO, there is some logic behind that. On charted visual approaches, I haven't seen a published MAP. My experience there is limited to DCA (River Visual 19 and MV Visual 1), LGA (River Visual 13 and Expressway Visual 31) and PHL (River Visuals 9L/R and Liberty Visual 27L. |
Originally Posted by CBreezy
(Post 1948161)
Just so we are clear, the AIM is not regulatory. It's best practices. You cannot be violated for AIM non-compliance unless it is determined that the action you took was reckless.
|
Originally Posted by Geardownflaps30
(Post 1948255)
I disagree with your last sentence. Reread what you wrote.
|
Originally Posted by CBreezy
(Post 1948161)
Just so we are clear, the AIM is not regulatory. It's best practices. You cannot be violated for AIM non-compliance unless it is determined that the action you took was reckless.
"Here is my argument to all those that say the AIM is not "regulatory"... "Where does it say you have to stop at a hold short line in the FARs?" Answer: NOWHERE! Only the AIM states this." I know there are other things the AIM states that you kind of have to do that aren't listed in any other regulations but I don't have time right now to look them up. But plenty of debate on whether the AIM is regulatory/mandatory online. And the ol reckless clause can be used on any deviation from the norm/"accepted best practices" in the AIM which effectively makes it regulatory at the FAA's whim. |
The one thing that I always come back to on these questions is this:
If I follow what my company's manuals say, I will not get in trouble. If I do not, there is a good chance that I will. Therefore, I always go with answer A. |
Originally Posted by Gearswinger
(Post 1948293)
The one thing that I always come back to on these questions is this:
If I follow what my company's manuals say, I will not get in trouble. If I do not, there is a good chance that I will. Therefore, I always go with answer A. |
And if the manual doesn't specify?
|
This is so simple, go around,
"Podunk Tower, Call sign, on the go, request closed" Tower can say either, "Closed approved, report base" or "Call sign, insert instructions, call radar on XXX.xx" GF |
| All times are GMT -8. The time now is 02:08 AM. |
Website Copyright © 2026 MH Sub I, LLC dba Internet Brands