ADVERTISEMENT



Google       

Home -> Law Blog Directory -> Legal Niches Blogs -> Aviation Law Discussions

OR PHONE (866) 635-1838 for Bankruptcy Help, (866) 635-6190 for Divorce,
(866) 635-2689 for Personal Injury or (866) 635-9402 for Criminal Defense

Find a Local Lawyer

Bankruptcy (866) 635-1838
Divorce (866) 635-6190
Personal Injury (866) 635-2689
Criminal Defense (866) 635-9402

Bookmark

Legal Niches

: Aviation Law Discussions

Aircraft Maintenance Records: What You Write Matters

By Reigel & Associates, Ltd.

ADVERTISEMENTS
If you repair or perform service on an aircraft, you are responsible for making a record of that work. Depending upon whether you are the aircraft owner or a mechanic, those records could include logbook entries, work cards, estimates, work orders and invoices. Unfortunately, if those records are not prepared carefully, and as required by the FARs, the person making the record could be exposing himself or herself to FAA enforcement action or civil liability.

For a more detailed discussion of this issue, please read my article on the topic here. Or, if you still have questions on the subject after reading the article, feel free to call.

Full post as published by Aviation Law Discussions on January 06, 2011 (boomark / email).

Bloggers, promote your law blog by nominating your blog for inclusion in USLaw.com's Law Blog Directory and RSS Reader. Benefits described.
Lawsuits and Settlements

Related Searches

























































































































US Law
#1 Online Legal Resource













Your Blog Subscriptions
Subscribe to blogs

10,000+ Law Job Listings
Lawyer . Police . Paralegal . Etc
Earn a law-related degree
Are you the author of this blog? Adding USLaw.com to your Blogroll increases relevance. You qualify to display a USLaw Network badge.
Suggest changes to this blog's description or nominate another for inclusion. Register for updates.


Practice Area
Zip Code:

Contact a Lawyer Now!






0.013 secs (new cache)