Originally Posted by mike734
I can't believe I pulled that one out but here is how I did it.
I figured 60kts is one mile a min so it would take 50 min. 120 would be 25 min and 240 would be 12.5 min. I knew I was going 250 not 240 so I just said 12 min. After the interview I figured 50 is one fifth of 250 therefore it would take one fifth of an hour. 60 divided by 5 is 12 miles.
I still did not get the job. (United)
mike, you mean "60 [minutes] divided by 5 is 12 [minutes]." Right?
ie. 50nm/250kts=0.2hr (12 mins).
How many milli-seconds did they give you to answer that?
If I got asked something like that during an interview I think I'd be itching to check it with the E6-B my wristwatch bezel; though I'm do wonder how well that would go over.
Would that be a major faux pas?
It would be ideal to be able to instantly crunch the numbers during an interview; but we all know how grueling those can be. If, for example you are nearing the end of the interview and you get asked that type of question (which is one that you could normally answer unaided) and you realize that you are starting to get brain fade, would it not be better to utilize the E6-B on your wristwatch and be sure of your answer, rather than not and so give only an approximate, or worse and give an incorrect answer?
If anyone has advice about handling this sort of scenario during an interview (ie. if it's ok/not ok to reference an E6-B) I'm all ears for it.