Mtns2Skies
Final Approach
- Joined
- Jul 12, 2008
- Messages
- 5,631
- Display Name
Display name:
Mtns2Skies
I am a student pilot, I know I couldn't log it but could I legally act as a safety pilot for a friend doing hood work?
I am a student pilot, I know I couldn't log it but could I legally act as a safety pilot for a friend doing hood work?
hahaha sounds like something i would say...Read 91.109(b) and come back and tell us the answer.
I wasn't sure where it was in the FAR's. Ah well delete the thread if its that obvious Greg
Which is one of the reasons I love having the FARs in electronic form, so I can search them!I would point out that since it's a pilot certification question, one's first inclination would be to look in Part 61, and I'm guesing that's where Austin looked -- and didn't find it. For whatever reason, the FAA chose to stick that part in the rule about needing a safety pilot when flying under the hood, rather than saying in Part 91 that you need a safety pilot and then saying who's allowed to be a safety pilot in Part 61 -- which would make more sense to me in terms of regulatory organization. Thus, it's a little hard for folks new to the game to find the rule on this point.
Actually Ron, I think that they are both official and legally current. It says at the top of the e-CFR I linked to that "e-CFR Data is current as of December 9, 2010" (that being Thursday, two business days ago) that it was the most recent. If you or someone is concerned that the FAA is putting out a regulation without notifying gpoaccess, they can certainly do a search in the one I linked to, find the appropriate part, and then look in the one you linked to in order to verify that there were no changes in the previous 2 business days.Only problem, Grant, is that site doesn't always have the latest changes to the FAR's. Only place to be sure of having the latest and greatest is the FAA's Regulatory and Guidance Library.
http://rgl.faa.gov/Regulatory_and_Guidance_Library/rgFar.nsf/MainFrame?OpenFrameSet
When will the e-CFR become an official edition of the CFR?
The Administrative Committee of the Federal Register (ACFR) has the authority under 44 U.S.C. 1510 to regulate the collation and republication of the Code of Federal Regulations (CFR) with the aim of keeping it as current as practicable. Until recently, it has not been economically practical to update the CFR more frequently than once per year. With the advent of web-based publication formats, the ACFR has requested that OFR and GPO develop and maintain the e-CFR as an authoritative informational resource, which will serve as the model for a currently updated, official edition of the CFR.
The e-CFR will be maintained as an unofficial editorial compilation until all remaining technical and performance issues are resolved. When those issues are satisfactorily resolved, the OFR/GPO partnership will propose to the ACFR that the e-CFR become an official edition of the CFR and a permanent record of the United States government.
Actually I think that they are both official and legally current. http://ecfr.gpoaccess.gov/cgi/t/tex...74b096e09875c6c8ca8de7ca5&c=ecfr&tpl=faq.tpl:
They may both be official, but they aren't both always up-to-date. I've found many times when the eCFR doesn't have changes already posted in the Federal Register and up on the FAA RGL site, sometimes for weeks or even months.Actually Ron, I think that they are both official and legally current.
Actually Ron, I think that they are both official and legally current. It says at the top of the e-CFR I linked to that "e-CFR Data is current as of December 9, 2010" (that being Thursday, two business days ago) that it was the most recent. If you or someone is concerned that the FAA is putting out a regulation without notifying gpoaccess, they can certainly do a search in the one I linked to, find the appropriate part, and then look in the one you linked to in order to verify that there were no changes in the previous 2 business days.
That said, This is on e-CFR at http://ecfr.gpoaccess.gov/cgi/t/tex...74b096e09875c6c8ca8de7ca5&c=ecfr&tpl=faq.tpl:
Just tried it....here's the error message:
Assertion failure (on ecfrlin1.access1.gpo.gov)
Message: No file for tpl=faq.tpl: in collection web space.
URL: http://ecfr.gpoaccess.gov/cgi/t/tex...00aa0;c=ecfr;tpl=faq.tpl:;page=simple;cc=ecfr
Stack trace:
Please report this error to: webadmin@gpo.gov
- DlpsUtils::ASSERT called from line 3440 in package TextClassUtils in file TextClassUtils.pm.
- Called by TextClassUtils::GetDefaultFileForCGC from line 175 in package TextClassUtils in file TextClassUtils.pm.
- Called by TextClassUtils::CgiToHtmlTemplate from line 457 in package TextApp in file /usr/local/dlxs/cgi/t/text/TextApp.pm.
- Called by TextApprocessRequest from line 266 in package TextApp in file /usr/local/dlxs/cgi/t/text/TextApp.pm.
- Called by TextApp::RunObjectMain from line 117 in package main in file /usr/local/dlxs/cgi/t/text/text-idx.
--------------------
Low bid contractor....
I haven't done any sort of statistical analysis of the recency of updates of the two sites. Apparently you have, so I'll defer to you here. I just noted that the gpoacess site gave a date 2 business days in the past (and today it says 12/10/10 on 12/14/10). The FAA site doesn't give a date at all. In general, I tend to go with the one that gives me the freshness date! Do you generally trust plates or charts without a date on them?They may both be official, but they aren't both always up-to-date. I've found many times when the eCFR doesn't have changes already posted in the Federal Register and up on the FAA RGL site, sometimes for weeks or even months.
I know better than to get between the two of you!And, BTW, it was R&W who brought this to my attention some time back.
Only problem, Grant, is that site doesn't always have the latest changes to the FAR's. Only place to be sure of having the latest and greatest is the FAA's Regulatory and Guidance Library.
http://rgl.faa.gov/Regulatory_and_Guidance_Library/rgFar.nsf/MainFrame?OpenFrameSet
...Plus, I tried to just put "No" as a response and they told me it was too short to post!