Possible Pilot Deviation - how long before hearing from FSDO?

  • Thread starter Thread starter Anon
  • Start date Start date
A

Anon

Guest
Was given a Brasher this past weekend in class B. Called the number given and the supervisor took my details and explained he process from the ATC side. I was cooperative and separately submitted an ASRS.

It’s now been 3 workdays since and nothing heard from the FSDO.

How long does it typically take for the FSDO to reach out to the pilot if they are going to?

I have only had one previous interaction with the FSDO and that was after declaring an emergency. That event also happened over a weekend, but I got a phone call on Monday morning for that one.
 
It takes a while for them to mobilize the Fugitive Apprehension Team. Just wait for the knock.. LOL

They will have to review tape/possibly talk with the controller and get back with you. I've heard of it taking a number of days to a couple of weeks.
 
How serious was the matter in question? IFR altitude 400’ off assigned? Turned into the final corridor for landing airliners?

Obviously, if a brasher is issued, it wasn’t TOTALLY a nothingburger, but from my observation, it seems that they may handle them differently or with different levels of urgency based on severity.

That’s totally just the observation of SGOTI, so take that for what it’s worth.
 
It may take several weeks so there is nothing to truly stress about right now. Being humble is your friend when they do call. Identify what you did whrong and explain what you are going to do to prevent doing it again in the future.
 
If you know what you did, might not be a bad idea to fly or do ground-school with a CFI to review whatever you felt short on. If you're able to show the FSDO guys that you're taking it seriously and are proactively trying to learn from the experience, it makes it a lot easier for them to slot you into the "compliance action" slot rather than a "violation" slot.
 
AvNavCom said:
If you know what you did, might not be a bad idea to fly or do ground-school with a CFI to review whatever you felt short on. If you're able to show the FSDO guys that you're taking it seriously and are proactively trying to learn from the experience, it makes it a lot easier for them to slot you into the "compliance action" slot rather than a "violation" slot.
Click to expand...

It doesn't become a violation (enforcement) as long as the airman is cooperative.
 
From experience(more than I’d like to admit), cooperation and willingness to learn sure beats stone walling and legal route.
 
Fully agree with the honest, introspective, humble approach. You might also file a NASA ASRS report ahead of time. While not a "Get out of Jail Free" card, it can certainly demonstrate your open and honest attitude. Personally, my experience was close to 15 years ago when an unforecasted storm cell forced me about 50 miles south of my planned scenic tour route in the Bay area. I had completely briefed the planned route beforehand, but my alternate route back to my home field put me in an area where I hadn't fully briefed the area. Unfortunately I clipped just the top edge of a small firefighting TFR coming over the mountains, which are somewhat common in the dry months in California. This was long before we had ADS-B updates in the plane. Upon landing, I got the dreaded "I have a number for you to call, advise when ready to copy". I went straight home and started typing my NASA report, explaining how the unplanned detour significantly south of my intended route put me in an unknown area, fully confessed my mistake, and noted the corrective actions I planned for the future. As stated above, the FSDO took a few weeks to get back to me. The FSDO agent was very understanding, and I got off with a simple warning.
 
Doc Holliday said:
It doesn't become a violation (enforcement) as long as the airman is cooperative.
Click to expand...
It *probably* won't be an enforcement action as long as the airman is cooperative. When I had my own inadvertent compliance action incidental to declaring an emergency, the FSDO guys made it clear to me that they are always free to go with either options, but the compliance action is strongly preferred if the pilot makes it easy.
 
AvNavCom said:
It *probably* won't be an enforcement action as long as the airman is cooperative. When I had my own inadvertent compliance action incidental to declaring an emergency, the FSDO guys made it clear to me that they are always free to go with either options, but the compliance action is strongly preferred if the pilot makes it easy.
Click to expand...

Not according to the applicable guidance. Enforcement can only happen if the airman refuses to cooperate or the deviation was deliberate.

You're also conflating terminology. You can read about Compliance Philosophy in the 8900.1 and the 2150.3.
 
Doc Holliday said:
Not according to the applicable guidance. Enforcement can only happen if the airman refuses to cooperate or the deviation was deliberate.

You're also conflating terminology. You can read about Compliance Philosophy in the 8900.1 and the 2150.3.
Click to expand...
That's fine. I just know what the FSDO guys told me when I was eyeballing them across a table. Perhaps they were just saying that it's their judgement as to whether a deviation was deliberate or not. Either way, I'm just passing along my direct experience with the process.
 
Back
Top