Gregory J. Reigel
Serving clients throughout the U.S.
Tel (214) 780-1482
Email: info@aerolegalservices.com

 
[Top Background]
Aviation Law Discussions Subscribe XML

A site devoted to aviation law, safety and security.

December 09, 2011

When Is A Flight Manual "Current" Under FAR 91.9(b)(1)?

In a recent Legal Interpretation, the FAA's Office of the Chief Counsel was asked whether an aircraft flight manual which was provided at the time that an aircraft was purchased would be considered the "current" flight manual for the purposes of FAR 91.9(b)(1) or whether the operator would need to have the latest revision of the manual in order to legally operate the aircraft.

The Interpretation initially noted that FAR 91.9(b)(1) "prohibits operation of an aircraft for which an [flight manual] is required if that aircraft does not contain a copy of the "current" approved [flight manual]". It then went on to observe that in order to comply with the Administrative Procedures Act ("APA"), the word "current" could not impose an ongoing obligation, but rather only apply as of the time that the manual was adopted by the owner or operator. However, the Interpretation qualified that observation by stating that a flight manual that was subsequently amended by an Airworthiness Directive ("AD") would be considered a "current, approved" flight manual for purposes of FAR 91.9(b)(1).

As a result, the Interpretation concluded that "the word 'current', as it is used in FAR 91.9(b)(1), refers to the version of the [flight manual] that was in place at the time that the aircraft in question was purchased and includes any subsequent AD-mandated changes that were made to the [flight manual]. It went on to explain that "[t]he word "current" does not encompass any subsequent changes that were made to the [flight manual] that were not mandated by an AD or other rulemaking because those changes did not go through the notice and comment rulemaking process."

Keep in mind that this Interpretation only applies to operations under FAR Part 91. Operations under other parts of the FARs are governed by different regulations which may interpret the word "current" differently than in the context discussed in this Interpretation. If you have questions or concerns regarding interpretations in other contexts, contact me directly and I would be happy to discuss the issue with you.

Posted by Greg

December 08, 2011

NTSB Proposes Amendment To Reporting Requirements For ACAS Advisories

In a Notice of Proposed Rulemaking published today the NTSB is proposing to amend the notification and reporting requirements of 49 CFR 830.5(a)(10) with regard to Airborne Collision and Avoidance System (ACAS) advisories. Currently the regulation requires ACAS advisory reporting "[w]hen an aircraft is being operated on an instrument flight rules flight plan and compliance with the advisory is necessary to avert a substantial risk of collision between two or more aircraft" or "to an aircraft operating in class A airspace."

Under the proposed amendment, the following ACAS advisories would need to be reported:
  1. When an aircraft is being operated on an instrument flight rules flight plan and compliance with the advisory is necessary to avert a substantial risk of collision between two or more aircraft; or

  2. To an aircraft operating in class A airspace, unless the advisory received only instructs the pilot to "monitor vertical speed."

According to the NTSB, it "believes the proposed change to section 830.5(a)(10) will continue to assist in achieving the NTSB's purpose of improving aviation [[Page 76688]] safety, while ensuring the language of the rule only requires notifications regarding specific ACAS advisories that the NTSB may seek to investigate."

Comments to the proposed amendment are due no later than February 6, 2012. If you would like more information, you may contact Scott Dunham, National Resource Specialist--ATC, Office of Aviation Safety, (202) 314-6387.

Posted by Greg

December 06, 2011

BARR Is Back In Business

The FAA announced in a December 2, 2011 Press Release that, "effective immediately, general aviation or on-demand charter aircraft owners or operators seeking to keep their aircraft’s registration number from being displayed over public data systems during flight no longer need to submit a Certified Security Concern to the FAA." As you may recall, on June 3, 2011 the FAA issued a policy that required aircraft owners or operators to submit a Certified Security Concern in order to have their aircraft tail number blocked from view on the FAA’s Aircraft Situation Display to Industry (ASDI) or National Airspace System Status Information (NASSI).

This change in policy represented a reversal of its longstanding implementation of BARR and allowing aircraft owners and operators to block their tail numbers without having to justify their reasons to the FAA. However, according to the Press Release, "[o]wners and operators seeking to have their aircraft tail number blocked from these data feeds can now submit a blocking request directly to the FAA without stating a reason for the request."

If you would like to have your tail number blocked, you may submit your blocking request to the FAA via e-mail. You should send the following information to the FAA at "CertifiedSecurityConcern@faa.gov":
  1. Aircraft owner or operator name;

  2. Email address the FAA can utilize to communicate with the aircraft owner/operator about the blocking request;

  3. Call sign (Tail Number) to be blocked - multiple tail numbers (call signs) can be submitted in one request; and

  4. Blocking level desired (ASDI Vendor Level or FAA).

If you don't have access to e-mail, you may submit your blocking request to the FAA via regular mail to: FAA Certified Security Concern, ATO System Operations Services, Room 1002, 800 Independence Avenue, SW, Washington, DC 20591.



Posted by Greg

December 05, 2011

FAA Maintains Percentage Rates For Random Drug And Alcohol Testing Of Safety-Sensitive Employees

In a Notice published December 1, 2011, the FAA stated "that the minimum random drug and alcohol testing percentage rates for the period January 1, 2012, through December 31, 2012, will remain at 25 percent of safety-sensitive employees for random drug testing and 10 percent of safety-sensitive employees for random alcohol testing." Since the reported random drug test positive rate for 2010 was less than 1.00% (it was actually 0.503%, down from 0.534% in 2009) and the minimum random alcohol test rate for 2010 was less than 0.50% (it was actually 0.011%, down from 0.088% in 2009) the FAA may continue the current rates for calendar year 2010. Interestingly, both of these actual rates have been declining since at least 2008.

For further information regarding the annual random testing percentage rates you should review FAR Part 120.109(b) (for drug testing), and FAR Part 120.217(c) (for alcohol testing) or you may contact Ms. Vicky Dunne, Office of Aerospace Medicine, Drug Abatement Division, Program Policy Branch (AAM–820), Federal Aviation Administration, 800 Independence Avenue SW., Room 806, Washington, DC 20591; Telephone (202) 267–8442.

Posted by Greg

Aviation Law Discussions - Archives

12/01/2003 - 12/31/2003
01/01/2004 - 01/31/2004
02/01/2004 - 02/29/2004
03/01/2004 - 03/31/2004
04/01/2004 - 04/30/2004
05/01/2004 - 05/31/2004
06/01/2004 - 06/30/2004
07/01/2004 - 07/31/2004
08/01/2004 - 08/31/2004
09/01/2004 - 09/30/2004
10/01/2004 - 10/31/2004
11/01/2004 - 11/30/2004
12/01/2004 - 12/31/2004
01/01/2005 - 01/31/2005
02/01/2005 - 02/28/2005
03/01/2005 - 03/31/2005
04/01/2005 - 04/30/2005
05/01/2005 - 05/31/2005
06/01/2005 - 06/30/2005
07/01/2005 - 07/31/2005
08/01/2005 - 08/31/2005
09/01/2005 - 09/30/2005
10/01/2005 - 10/31/2005
11/01/2005 - 11/30/2005
12/01/2005 - 12/31/2005
01/01/2006 - 01/31/2006
02/01/2006 - 02/28/2006
03/01/2006 - 03/31/2006
04/01/2006 - 04/30/2006
05/01/2006 - 05/31/2006
06/01/2006 - 06/30/2006
07/01/2006 - 07/31/2006
08/01/2006 - 08/31/2006
09/01/2006 - 09/30/2006
10/01/2006 - 10/31/2006
11/01/2006 - 11/30/2006
12/01/2006 - 12/31/2006
01/01/2007 - 01/31/2007
02/01/2007 - 02/28/2007
03/01/2007 - 03/31/2007
04/01/2007 - 04/30/2007
05/01/2007 - 05/31/2007
06/01/2007 - 06/30/2007
07/01/2007 - 07/31/2007
08/01/2007 - 08/31/2007
09/01/2007 - 09/30/2007
10/01/2007 - 10/31/2007
11/01/2007 - 11/30/2007
12/01/2007 - 12/31/2007
01/01/2008 - 01/31/2008
02/01/2008 - 02/29/2008
03/01/2008 - 03/31/2008
04/01/2008 - 04/30/2008
05/01/2008 - 05/31/2008
06/01/2008 - 06/30/2008
07/01/2008 - 07/31/2008
08/01/2008 - 08/31/2008
09/01/2008 - 09/30/2008
10/01/2008 - 10/31/2008
11/01/2008 - 11/30/2008
12/01/2008 - 12/31/2008
01/01/2009 - 01/31/2009
02/01/2009 - 02/28/2009
03/01/2009 - 03/31/2009
04/01/2009 - 04/30/2009
05/01/2009 - 05/31/2009
06/01/2009 - 06/30/2009
07/01/2009 - 07/31/2009
08/01/2009 - 08/31/2009
09/01/2009 - 09/30/2009
10/01/2009 - 10/31/2009
11/01/2009 - 11/30/2009
12/01/2009 - 12/31/2009
01/01/2010 - 01/31/2010
02/01/2010 - 02/28/2010
03/01/2010 - 03/31/2010
04/01/2010 - 04/30/2010
05/01/2010 - 05/31/2010
06/01/2010 - 06/30/2010
07/01/2010 - 07/31/2010
08/01/2010 - 08/31/2010
09/01/2010 - 09/30/2010
10/01/2010 - 10/31/2010
11/01/2010 - 11/30/2010
12/01/2010 - 12/31/2010
01/01/2011 - 01/31/2011
02/01/2011 - 02/28/2011
03/01/2011 - 03/31/2011
05/01/2011 - 05/31/2011
06/01/2011 - 06/30/2011
07/01/2011 - 07/31/2011
08/01/2011 - 08/31/2011
09/01/2011 - 09/30/2011
10/01/2011 - 10/31/2011
11/01/2011 - 11/30/2011
12/01/2011 - 12/31/2011
01/01/2012 - 01/31/2012
02/01/2012 - 02/29/2012
03/01/2012 - 03/31/2012
04/01/2012 - 04/30/2012
05/01/2012 - 05/31/2012
06/01/2012 - 06/30/2012
07/01/2012 - 07/31/2012
08/01/2012 - 08/31/2012
10/01/2012 - 10/31/2012
11/01/2012 - 11/30/2012
12/01/2012 - 12/31/2012
02/01/2013 - 02/28/2013
04/01/2013 - 04/30/2013
05/01/2013 - 05/31/2013
06/01/2013 - 06/30/2013
07/01/2013 - 07/31/2013
08/01/2013 - 08/31/2013
11/01/2013 - 11/30/2013
12/01/2013 - 12/31/2013
01/01/2014 - 01/31/2014
02/01/2014 - 02/28/2014
05/01/2014 - 05/31/2014
07/01/2014 - 07/31/2014
08/01/2014 - 08/31/2014
10/01/2014 - 10/31/2014
12/01/2014 - 12/31/2014
01/01/2015 - 01/31/2015
03/01/2015 - 03/31/2015
04/01/2015 - 04/30/2015
06/01/2015 - 06/30/2015
07/01/2015 - 07/31/2015
08/01/2015 - 08/31/2015
10/01/2015 - 10/31/2015
12/01/2015 - 12/31/2015
03/01/2016 - 03/31/2016
07/01/2016 - 07/31/2016
08/01/2016 - 08/31/2016
10/01/2016 - 10/31/2016
01/01/2017 - 01/31/2017
02/01/2017 - 02/28/2017
03/01/2017 - 03/31/2017
04/01/2017 - 04/30/2017
05/01/2017 - 05/31/2017
06/01/2017 - 06/30/2017
07/01/2017 - 07/31/2017
08/01/2017 - 08/31/2017
09/01/2017 - 09/30/2017
10/01/2017 - 10/31/2017
11/01/2017 - 11/30/2017
12/01/2017 - 12/31/2017
01/01/2018 - 01/31/2018
02/01/2018 - 02/28/2018
03/01/2018 - 03/31/2018
05/01/2018 - 05/31/2018
07/01/2018 - 07/31/2018
08/01/2018 - 08/31/2018
09/01/2018 - 09/30/2018
10/01/2018 - 10/31/2018
12/01/2018 - 12/31/2018
01/01/2019 - 01/31/2019
02/01/2019 - 02/28/2019
04/01/2019 - 04/30/2019
05/01/2019 - 05/31/2019
07/01/2019 - 07/31/2019
08/01/2019 - 08/31/2019
09/01/2019 - 09/30/2019

< ? law blogs # >

The information contained in this web-site is intended for the education and benefit of those visiting the Aero Legal Services site. The information should not be relied upon as advice to help you with your specific issue. Each case is unique and must be analyzed by an attorney licensed to practice in your area with respect to the particular facts and applicable current law before any advice can be given. Sending an e-mail to Aero Legal Services or Gregory J. Reigel does not create an attorney-client relationship. Advice will not be given by e-mail until an attorney-client relationship has been established.

© Gregory J. Reigel-Aero Legal Services 2002-Present. All rights reserved.