Someone on here made a comment on what a great bunch of guys the FAA are. Try this one on. I personally know the individuals involved.
A local aircraft had a hard landing and was incorrectly pieced back together. A local AI saw the work and reported it to the FAA FSDO who said they would deadline the aircraft. Two months later the FSDO had not contacted the owners and the aircraft comes apart in flight, killling the two occupants. Everyone knew exactly where the aircraft was, it was not hidden.
Now the zinger: The local FSDO tells the AI to be quiet or he may have his license revoked.
I got this directly from the parties involved. I have flown in the aircraft involved and know the original owner and AI very well.
Second case. Repair station/QA manual written as a single document per FAA written guidelines document. After several sessions with FAA without any comment as to this being a problem the FSDO suddenly questions it being a single document. Shown the FAA guide they reply, "Oh, we've never seen that before."
Shown the specific examples of how the guide says the document can be combined as one they reply after much hemming and hawing, "That isn't really what it means."
Author of Repair manual exits FSDO, tells prospective manager of Repair Station that he is not prepared to deal with bureaucratic morons any further and throws manual in trash can.
Please no more of what a fine organization the FAA is, ok.
DC
A local aircraft had a hard landing and was incorrectly pieced back together. A local AI saw the work and reported it to the FAA FSDO who said they would deadline the aircraft. Two months later the FSDO had not contacted the owners and the aircraft comes apart in flight, killling the two occupants. Everyone knew exactly where the aircraft was, it was not hidden.
Now the zinger: The local FSDO tells the AI to be quiet or he may have his license revoked.
I got this directly from the parties involved. I have flown in the aircraft involved and know the original owner and AI very well.
Second case. Repair station/QA manual written as a single document per FAA written guidelines document. After several sessions with FAA without any comment as to this being a problem the FSDO suddenly questions it being a single document. Shown the FAA guide they reply, "Oh, we've never seen that before."
Shown the specific examples of how the guide says the document can be combined as one they reply after much hemming and hawing, "That isn't really what it means."
Author of Repair manual exits FSDO, tells prospective manager of Repair Station that he is not prepared to deal with bureaucratic morons any further and throws manual in trash can.
Please no more of what a fine organization the FAA is, ok.
DC
Comment