Backcountry Pilot • Aviation Statute of Limitations - variable

Aviation Statute of Limitations - variable

Discuss the legality of flying the backcountry, FARs, advocacy, and aviation relevant legislation. Registered users only.
6 postsPage 1 of 1

Aviation Statute of Limitations - variable

I have seen others ask if there is any statute of limitations in FAA rules.
I may have found a source and a table.

Below link goes to a LOONNGG document but there is a chart below Fig 4.1
just not able to get it to come over as a chart. ORDER 2150.3 effective 10-01-07
Looks like we have a better chance than I originally thought.

Disclaimer is I have never been hit with it. Been told to call the tower a couple times but I just reply back for them to go review 14 CFR 91.3. No call backs.

http://fsims.faa.gov/WDocs/Orders/2150_3B.htm


FIGURE 4.1 TIME LIMITATIONS APPLICABLE TO ALL LEGAL ENFORCEMENT ACTIONS FOR VIOLATIONS ON OR AFTER DECEMBER 12,
2003.


Currently unable to make the chart fit without it getting all scrambled with NO chart outline. Maybe someone else can wrap it up.

Wannabe Hopeful.

May try to reconstruct the chart into an Excel file and see what happens. some day.
wannabe offline
User avatar
Posts: 782
Joined: Mon Aug 06, 2007 10:12 am
Location: Palo Alto, Calif.
53 C-170-B+

It is better to be late in this world, than early in the next.

Re: Aviation Statute of Limitations - variable

Thanks for finding this. The enormous size of the document itself speaks volumes.

It looks like the "stale" period requires the FAA to notify a suspected violator within 6 months of the violation. There are exceptions for more serious things that could result in revocation of certificates based on lack of qualifications, or fines over $50k. On the plus side, the ASRS report remains an immediate "get out of jail" card for unintentional violations. Pretty important in this era of the perpetual pop-up TFR threat.

Section 5 explains the shorthand that's in Table 4.1:

5. Time Limitations in Cases Involving Certificate Suspensions or Revocations. Cases involving the suspension or revocation of airman, type, production, airworthiness, air carrier operating, airport operating, air agency and air navigation facility certificates are reviewed by the NTSB. Section 821.33 of the NTSB’s Rules of Practice in Air Safety Proceedings (49 C.F.R. part 821), known as the stale complaint rule, provides that an FAA complaint (order) may generally be dismissed if the offenses alleged occurred more than six months prior to the Administrator’s advising a respondent of the reasons for the proposed action. Advising the respondent refers to the respondent’s receipt of the legal document sent by FAA legal counsel proposing the certificate action.

a. Exceptions to Stale Complaint Rule.

(1) The first exception involves cases in which the FAA’s complaint alleges the certificate holder lacks qualifications to hold the certificate (for example, revocation cases). In these cases, the 6-month rule does not apply. The FAA does not use revocation as a means to avoid dismissal of charges under the stale complaint rule. Although the 6-month stale complaint rule does not apply to qualifications cases, the FAA expedites such cases because they generally involve significant safety issues.

(2) The second exception to the 6-month stale complaint rule involves cases in which the FAA can show that it had good cause for not meeting the 6-month deadline. The most common good cause circumstance is found in late-discovery cases, in which the FAA discovers the violation after the date of violation. In these cases, however, the FAA does not have an extra six months from the date of late discovery to issue its notice. Rather, the FAA must put its investigation of these cases on a fast track, and must document priority handling at all stages of the investigation and review. Contemporaneously created documents and notes tracking what the investigating office did during the investigation are persuasive in showing that the FAA gave a case priority handling.

(3) The third exception to dismissal under the stale complaint rule is when the imposition of a sanction is in the public interest despite the delay. This situation is rarely, if ever, found by the NTSB.

b. Definitions.

(1) Date of violation. The date the respondent violated the regulation. This date starts the 6-month stale complaint period.

(2) Date known to FAA. The date the FAA knew or reasonably should have known of the likelihood of a violation. This date is not the date FAA investigating personnel determined there was a violation; rather, it is the date preliminary information was received that triggered or should have triggered an investigation.

(3) Priority handling. Priority handling means the FAA investigative office must process this case before all other non-emergency matters. This may mean that cases must be reassigned within an office, because, generally, it is not diligent handling if case processing is delayed because an employee is in training or on leave.

c. Examples.

(1) An FAA air traffic controller observes a violation on January 1. FAA investigative personnel receive the pilot deviation report on May 1. This case goes stale on July 1. FAA investigative personnel and FAA legal counsel must process this case with priority handling so the alleged violator receives the notice before July 1.

(2) A mechanic performs poor maintenance on February 1 but the violation is not discovered until July 15 following an accident. The case goes stale on August 1. However, the investigation is complex and cannot be finished before August 1. Therefore, the investigation must be given priority handling so that the agency can show good cause for the delay.

(3) A mechanic performs a 100-hour inspection and approves the aircraft for return to service on January 1. The following January, another mechanic inspects the aircraft and the
owner reports to the FAA that an airworthiness directive was due and not complied with at the time of the previous inspection. The FAA could go forward with a notice of proposed certificate action only if the investigative office can document that it processed the case expeditiously as a priority matter.

(4) A mechanic commits a maintenance violation on January 1. An FAA inspector discovers the violation on April 1 and starts an investigation. On May 30, the inspector goes to Oklahoma City, Oklahoma for six weeks of training. During his or her absence, the office does not reassign the case and does not do any work to further the investigation. On the inspector’s return to the office in mid-July, the case is stale and the case cannot go forward because the office cannot show priority handling.


There's a lot more about fines, investigations etc. etc. but this appears to be the part that's most relevant to part 91 pilots.

CAVU

CAVU
CAVU offline
User avatar
Posts: 659
Joined: Wed May 10, 2006 4:54 pm

Re: Aviation Statute of Limitations - variable

wannabe wrote:Been told to call the tower a couple times but I just reply back for them to go review 14 CFR 91.3. No call backs.



Forgive the ignorance on my side, but I am not sure what you mean by no call backs. I reviewed 91.3; are you referring to the requirement to file in writing when deviating in an emergency as the reason for not calling ATC when asked?

I have had my share of call back's when flying 135 and they were all positive and constructive. However I have never had a call back request flying 91 and want to make sure I am am properly calibrated if I do get such a request when flying 91.

How do folks handle this when pleasure flying?

Thanks for posting this info, btw.

Thanks, M3X
M3X offline
Posts: 115
Joined: Thu Sep 04, 2014 8:01 pm
Location: Livermore

Re: Aviation Statute of Limitations - variable

M3X

I have twice been landing at Palo Alto in the evening, sun partially in my face, four people in a 172, cleared to land, (with one plane that missed a turn off so was coasting to the far end) I was into the flare, with full flaps, and settling, when the tower tells me to "GO AROUND" by the time he finished those two words I was down and lowering the nose wheel. I was stopped at the second turnoff - waiting for the first plane to taxi by when the tower told me to call the tower after I parked.
I told him to go read 91.3. I was not about to abort a landing that far in, with a couple in the back who had never flown before. The tower made no more radio calls, I switched to ground and ground did not seem excited. Suspected a tower trainee was at the mike. I did not even have time to reach for the panel mounted mike before the wheels touched. Also I had come in slower just to help out with the towers spacing problem. Palo Alto A/P sits down below sea level with high dikes close on three sides, can turn dark in the "bottom" at flare. Hope that helps.

If I had been alone, 20 degrees flaps, I probably would have just said, "OK Boss."
But NOT with the lives of admittedly nervous others. No smileys with this one!

Wannabe calming back down.
wannabe offline
User avatar
Posts: 782
Joined: Mon Aug 06, 2007 10:12 am
Location: Palo Alto, Calif.
53 C-170-B+

It is better to be late in this world, than early in the next.

Re: Aviation Statute of Limitations - variable

M3X wrote:.......I have had my share of call back's when flying 135 and they were all positive and constructive. However I have never had a call back request flying 91 and want to make sure I am am properly calibrated if I do get such a request when flying 91.....


I would say just keep calm and avoid failing the attitude check.
Easily said but not so easily done.
A buddy of mine was told to call ATC after we took off at KOKH when skydivers were in the air over it.
Although he was in contact with ATC per FAR 105.13, the jump pilot (as usual) was lax in making calls on the CTAF freq per AIM 3-5-4 so we had no idea that jumpers were in the air. My buddy explained that to the Navy Whidbey controller, and was told that he should have called the Navy ATC freq before takeoff-- although you can't reach them from the ground at KOKH. He handled it well, if I'd been the one told to call ATC it probably wouldn't have turned out too well. Hard to keep myself in check when getting chewed out for someone else's fuckup. Several things I have heard on the radio indicate to me that the Navy Whidbey controllers don't really get it when it comes to civilian skydiving ops-- I think they're more used to op's inside TFR's and alert/restricted/prohibited areas, and tend to treat civilian skydiving in a similar fashion.
hotrod180 offline
Supporter
User avatar
Posts: 10534
Joined: Wed Jan 26, 2005 11:47 pm
Location: Port Townsend, WA
Cessna Skywagon -- accept no substitute!

Re: Aviation Statute of Limitations - variable

wannabe wrote:Hope that helps.
It does; thanks for taking the time.


hotrod180 wrote: Easily said but not so easily done.
Again, appreciate the impressions.



I appreciate the way lots of folks will read a post, and those that have something to add will do so. Whereas on some forums, folks seem to need to post just to hear themselves speak.

In short seeing lots of views, and a couple of thoughtful posts indicates both the value of these posts, but implies some level of consensus from this community, which is in itself valuable.

Forgive the thread drift, but I guess I am pointing out the silent majority actually do add value to the conversation, in this sort of community.


-M3X
M3X offline
Posts: 115
Joined: Thu Sep 04, 2014 8:01 pm
Location: Livermore

DISPLAY OPTIONS

6 postsPage 1 of 1

Who is online

Users browsing this forum: No registered users and 0 guests

Latest Features

Latest Knowledge Base