The FAA is after me!
#23
Gets Weekends Off
Joined APC: Feb 2007
Position: 767 CA
Posts: 217
I had the same thing happen while flying a Falcon in 2004 which resulted in a loss of separation. The FAA issued a letter of warning which was erased from my PRIA records two years later. From your previous post, it sounds like there was no loss of separation with your incident, so I can’t imagine that they would even give you a letter in your file. There were some extenuating circumstances that contributed to my situation, one being that controller error was deemed a factor by the FAA. Even with that being said, I don’t think your incident was even close to what warrants enforcement action. Trust me, your predicament is not as bad as it may seem. Feel free to PM me if you have any further questions.
#24
If you don't have union help AOPA has legal help and a panel of attorneys,,
Any and all thoughts would be most welcome.
Had a situation a few months ago where the combination of a very excited passenger, (pvt. pilot) and a faulty altitude capture mode caused us to deviate altitude +300 feet at FL350. We caught the problem but rather than push the nose over and put the passenger into the ceiling, we had him return to his seat and decended to FL350. We were high for about 30 secs. Denver center has us call them to explain. There was no loss of seperation. Now the Denver FSDO is taking a look at this and I am worried this might become A "ding" on my record. Anyone with a similar experience?
Any advice would be great.
Cheers.
Had a situation a few months ago where the combination of a very excited passenger, (pvt. pilot) and a faulty altitude capture mode caused us to deviate altitude +300 feet at FL350. We caught the problem but rather than push the nose over and put the passenger into the ceiling, we had him return to his seat and decended to FL350. We were high for about 30 secs. Denver center has us call them to explain. There was no loss of seperation. Now the Denver FSDO is taking a look at this and I am worried this might become A "ding" on my record. Anyone with a similar experience?
Any advice would be great.
Cheers.
#25
On Reserve
Joined APC: Apr 2008
Posts: 13
I agree with Socal Swede. I did get a lawyer and he did the talking to the appropriate people and I got a Warning Letter as it was my first offense with the FAA. It's a Warning Letter. I, too, filed a NASA report at the beginning to cover my backside. Hope this helps.
#26
Line Holder
Joined APC: Feb 2008
Position: Anything available/Right
Posts: 32
I filed one as soon as I landed. Got the recipt in the mail a few weeks ago. I know it offers some protection, but for the life of me I can't understand why the Denver FSDO has such a hard on for this. I heard a SWA crew "bust" an altitude but the center didn't have them make a call.
Last edited by kt61; 04-14-2008 at 04:43 PM. Reason: addition
#27
Gets Weekends Off
Joined APC: May 2007
Posts: 165
Jetjock
PM me I will give you info and contacts . Had this happen to me, also have a small company that works with attorneys. Most important don't talk or write to FAA. Also don't let ANYONE know you have NASA form yet.
30west
ps off to LHR wed-fri
PM me I will give you info and contacts . Had this happen to me, also have a small company that works with attorneys. Most important don't talk or write to FAA. Also don't let ANYONE know you have NASA form yet.
30west
ps off to LHR wed-fri
#29
On Reserve
Joined APC: Sep 2006
Posts: 19
"If you really had a "faulty" Alt Cap and wrote it up then you are off the hook before you ever got on. You still may be able to use the issue to slide right off the hook nice and easy like even if wasn't written up and you can explain how it was still an automation glitch you had to recover from."
Case in point for contacting a lawyer or union rep......get correct info.
Doesn't matter if you wrote it up or not, automation glitch or not, etc.
You take it in the air, you are responsible for flying by the rules.
If it doesn't capture, kick off the autopilot and make it capture the alt. Same for Navigation errors......it it doesn't fly the correct route, make it fly the correct route. Either that or make the mech. fix it first.
Case in point for contacting a lawyer or union rep......get correct info.
Doesn't matter if you wrote it up or not, automation glitch or not, etc.
You take it in the air, you are responsible for flying by the rules.
If it doesn't capture, kick off the autopilot and make it capture the alt. Same for Navigation errors......it it doesn't fly the correct route, make it fly the correct route. Either that or make the mech. fix it first.
Thread
Thread Starter
Forum
Replies
Last Post