Originally Posted by phiggsbroadband
(Post 10808435)
As an ex endurance event cyclist, I think that Dehydration, and Hunger Bonk will be part of the cause of this accident.
Plenty of people have crashed aircraft in a stupid way whilst fully fed and watered... |
Is ignoring ATC a common thing?
(SLF) After reading through this thread I haven't seen an answer to this question I am having: is it a common thing for the PIC to simply ignore a given vector by ATC and bluntly answer that they are fine and won't comply?
|
There would have to be justification to decline an ATC instruction. In this case the aircraft had established on the ILS (albeit grossly not stable) and the Captain was ‘comfortable’ with the situation, despite the circumstances which tragically unfolded.
|
There is a PIA website where at least one post refers to both pilots fasting. Shouldn't be too hard to find. My detailed information or research indicating the reasons why "cultural" matters could have contributed to this accident were removed by the moderator, apparently under "moderator discretion" rather than specific posting rules.
It would be an improvement if posters would avoid an attempt at political correctness re dehydration. |
Originally Posted by lomapaseo
(Post 10808757)
I'm not trying to be complete here,I'm just trying to understand what you really want. and why. |
Originally Posted by autoflight
(Post 10808955)
There is a PIA website where at least one post refers to both pilots fasting. Shouldn't be too hard to find. My detailed information or research indicating the reasons why "cultural" matters could have contributed to this accident were removed by the moderator, apparently under "moderator discretion" rather than specific posting rules.
It would be an improvement if posters would avoid an attempt at political correctness re dehydration. |
Because it crashed.
|
Originally Posted by Longtimer
(Post 10808972)
Regarding Fasting, that has been the case for Muslim air crew for many/many years with no reported problems. Why would this one be different?
|
Like everything else. Including the observation that everything was discussed earlier in the thread.
|
As previously mentioned wait for 22 June ~ Interim Report to be published
|
Originally Posted by aterpster
(Post 10808961)
It's not what I want. It is what the NTSB detailed docket provides for accidents under their jurisdiction. Very full disclosure and transparency.
|
Originally Posted by ATC Watcher
(Post 10808770)
As I explained already at the beginning of this thread , TWR controllers cannot issue a Go around instruction for that reason, Once a PIC reports established on the ILS ,he is on his own , It is up to them to manage his approach .TWR Controllers should not interfere unless the runway is blocked or becomes not avail . In addition in many modern Towers you cannot monitor the approach anyway ( too far away )
|
Originally Posted by DaveReidUK
(Post 10808796)
While a new tower at OPKC has been planned for several years, the current one (built in 1932) is atop the original terminal, not particularly high, and about 3/4 of the way down the runway from the 25 end (around 2.6 km from the 25L piano keys).
|
Originally Posted by homebuilt
(Post 10809173)
I know that !! But if I were an ATC controller watching a supposedly routine flight flaring gear up afew feet above the runway, I couldn't help yelling on the radio in order to warn the crew of the situation. "XXXX Go around !!" could be the first sentence coming into my mind. It would be a reflex and meanwhile I wouldn't think about the rules and the lawyers. Time for that later.
Report will (should) tell but it seems to me that TWR's inaction is unlikely to play a significant part in probable cause |
Originally Posted by parkfell
(Post 10808881)
There would have to be justification to decline an ATC instruction. In this case the aircraft had established on the ILS (albeit grossly not stable) and the Captain was ‘comfortable’ with the situation, despite the circumstances which tragically unfolded.
|
If I were an ATC controller watching a supposedly routine flight flaring gear up afew feet above the runway, I couldn't help yelling on the radio in order to warn the crew of the situation. "XXXX Go around !!" could be the first sentence coming into my mind. It would be a reflex and meanwhile I wouldn't think about the rules and the lawyers. Time for that later. If you were watching a take off, and you saw flames coming from an engine, you would probably tempted to shout "Stop!". |
No Gear, go round would perhaps be a better call. Less likely focussed pilot would ignore the interfering ATC person!
|
Originally Posted by Maninthebar
(Post 10809191)
Do we know that the gear were up during the approach? Or did they transit up owing to a botched GA process?
Report will (should) tell but it seems to me that TWR's inaction is unlikely to play a significant part in probable cause |
Originally Posted by 16024
(Post 10809213)
This is where it gets difficult.
If you were watching a take off, and you saw flames coming from an engine, you would probably tempted to shout "Stop!". But anyway I'm not an ATC controller, and beeing closer to retirement than to CPL-IR course, I've no plans to start a new career..:rolleyes: |
Originally Posted by donotdespisethesnake
(Post 10809203)
I am a bit puzzled how that squares with a non-compliance report made by ATC controller, and formal notice sent to PIA regarding. https://www.aviation-accidents.net/w...ht-pk8303-.pdf
The other question is whether a report (MOR?) would have been raised had the tragic events not have occurred? With the benefit of hindsight approach radar controller should have notified the aerodrome controller that is was decidedly “iffy” and instructed a Go-Around. Was he transferred to tower frequency? A time that you are required to do as you are told might be, for example : “I am instructed by Her Majesty Government to refuse you entry into United Kingdom Airspace. What are your intentions? Failure to comply would be followed by a QRA by air defence......... There may well be others......yet to be pointed out |
All times are GMT. The time now is 22:18. |
Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.