The FAA is after me!
12-28-2008, 02:32 PM
#41
Line Holder
Joined APC: Jan 2008
Posts: 92
Originally Posted by Purpledriver
Did you file a NASA report? Too late now, but that could have saved you.
12-28-2008, 05:11 PM
#43
Gets Weekends Off
Joined APC: Nov 2006
Posts: 585
Originally Posted by GolfKilo
Purple is right...a NASA report is a "get out of jail" card. They can't touch you if you file a report within 24 hours of the incident, IF the incident is unintentional. Believe me, I know. I'm a retired FAA controller, now flying a CE550 Pt. 135. I keep a stack of those suckers in my flight bag! Good luck!
It's ten days for ASRS, and yes the FAA can touch you: Remedial Training, 709 ride, administrative letter of warning, administrative letter of correction, and a few others. They can even demand to revoke your certificate, which the sentence will be listed in your records, but will not require the actual surrender of the certificates due to the penalty waiver. It's a get-out-of-jail-almost-free program.
12-28-2008, 07:08 PM
#44
Prime Minister/Moderator
Joined APC: Jan 2006
Position: Engines Turn Or People Swim
Posts: 39,261
Originally Posted by jedinein
It's ten days for ASRS, and yes the FAA can touch you: Remedial Training, 709 ride, administrative letter of warning, administrative letter of correction, and a few others. They can even demand to revoke your certificate, which the sentence will be listed in your records, but will not require the actual surrender of the certificates due to the penalty waiver. It's a get-out-of-jail-almost-free program.
12-29-2008, 09:14 AM
#45
Gets Weekends Off
Joined APC: Jun 2008
Position: On top.
Posts: 167
I hope it all worked out for you.
But, automation is there to help you, but please pay attention to what you are doing. One of the first things you have learned in training is to "fly the airplane".
Whatever happened with your passenger could, and absolutely should, have been postponed till after you leveled off at FL350. You have nothing to do between 34,500 and 35,000 but one thing: to make sure that it levels off.
It might even make a point to them (your company, future companies, the FAA, the JAA and whoever else you might work for at some point) that you might not have been in control of your airplane as a PIC. That would be my biggest concern.
But, automation is there to help you, but please pay attention to what you are doing. One of the first things you have learned in training is to "fly the airplane".
Whatever happened with your passenger could, and absolutely should, have been postponed till after you leveled off at FL350. You have nothing to do between 34,500 and 35,000 but one thing: to make sure that it levels off.
It might even make a point to them (your company, future companies, the FAA, the JAA and whoever else you might work for at some point) that you might not have been in control of your airplane as a PIC. That would be my biggest concern.
12-30-2008, 12:34 PM
#47
Gets Weekends Off
Joined APC: Apr 2008
Position: Bus
Posts: 768
I have had to "strangle" my mode C before in the military until a "correction" was made. Controller asked about alt encoding, said we would recycle and wouldn't you know we were on altitude after we recycled.
12-30-2008, 01:15 PM
#48
Gets Weekends Off
Joined APC: Oct 2006
Position: 737
Posts: 590
Originally Posted by Jetjock13
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.
12-30-2008, 02:01 PM
#49
Gets Weekends Off
Joined APC: Jun 2008
Position: Reclined
Posts: 2,168
General rule of thumb after any type of deviation.
1 write up the offending equipment
2 file an ASAP
3 file an ASRS (NASA form)
4 When dealing with the FAA
A If talking about future events and planning - glad to help, lets chat.
B If talking about past events - sorry, no comment at this time
1a If option B ocurrs - contact your union, your union attorney
and consider locating your own attorney.
1 write up the offending equipment
2 file an ASAP
3 file an ASRS (NASA form)
4 When dealing with the FAA
A If talking about future events and planning - glad to help, lets chat.
B If talking about past events - sorry, no comment at this time
1a If option B ocurrs - contact your union, your union attorney
and consider locating your own attorney.
Thread
Thread Starter
Forum
Replies
Last Post
