If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
The thread isn't dead, but it sure has been napping. I don't know about the others but I haven't been able to break away to work on my plane for several weeks. Just a couple of quick trips to the airport.
I think I am going through "T" withdrawal.
Hank
That was some good dialog above. I'm certainly not a lawyer but working for Corporate America has tuned me into the legal department’s way of thinking. I would think verbiage such as 'Taylorcraft Recommended Annual Maintenance' or something similar would do the trick. Obviously the IA is liable for anything in FAR43 Appendix D, but he can supplement it with anything else he decides to do unless it compromises airworthiness. The person on the stand would be the person with the most money and since the T-Craft organization isn’t spilling over with $$$, I don’t see it has too much to worry about legally. Also, thinking of the IA (I was one before letting it lapse) if he was ever investigated or subpoenaed; his defense would be that he used 43 Appendix D as the inspection and included the following as part of the maintenance ie: Taylorcraft Recommended Annual Maintenance. Keep in mind an inspection checklist can be of ones own design as long as it ‘includes’ all items in App. D. I have never heard of anybody getting dinged by the feds for doing to much inspecting or maintenance unless they left something loose in doing so. Just throwing it out there to mull over…….
How about we start collecting and culling items and see how it goes. Just call it "Inspection Suggestions," or "Inspection Ideas" for now. I'm sure I will have a few to throw in--
Darryl
Can we create a controlled location on the site to put the document? It will get lost in the fog if we try to maintain it on this thread. We should discuss it here and store it someplace that one (or a few) people make the entries but everyone can read it.
Hank
For now I suggest we call it something simple like "The maintenance document". We can discuss the proper title here.
Can one of the computer literate folks set up the location for the document and maybe start it out with the annual section of 43 Appendix D? The drain hole in the gear is a perfect example of what should be added to the list.
Hank
Let’s just use this thread as the location for the doc. I'm happy to post it (Wells Fargo owns my house so sue away!!!). If you want to send me the information we have already put together as well as pics or drawings, I am happy to compile it and post it. My e-mail is [email protected]. I can work on it in the next week or so. I am not going to sweat the 'title'. I'll just throw in some disclaimer and call it good. We can use this thread to keep posting ideas and I can do revisions as necessary. It's time to quit talking about it and take some action. I'm raising my hand if you're interested.
This is a great idea. There's no way that App. D covers all the nuances of a specific model of airplane. Take the Shinn brakes for example. App. D would state: Inspect brakes for wear and condition. In the T-Craft supplement: Check horseshoe cam angles for wear at the contact point of brake shoe. Make sure adjustment wedges work freely and are not worn excessively. Robert Lee's brake doc could then be linked or referenced.....possibilities are endless. Let’s get it started and polish it as we go.
I guess you have me there. The reason I suggested another location for the document itself is I have no idea how to put it into a discussion thread and then modify it and track the changes.
I actually don't care how we do it or where, I just don't personally know HOW we can do it here. Jump in and I will help however I can, but I am awful with computers.
Hank
This was all I was going to do Hank. I will play with this site more but I think you can get notifications when something changes on a thread etc... I think we could do something with groups too. That’s what that subscribe stuff is all about. It will even trigger e-mails. I'm not a URL guy but a dedicated web address could also be used for the document. That’s a little out of my league though. I noticed Victor Bravo also volunteered early in the thread. I'm certainly not trying to step on toes, but am certainly willing to help. Also...I would think once we have a nice document completed, we could get the Foundations web administrator to link it from the website. Not a big deal for people that scriped HTML etc...
My concern wasn't with creating a document, just that I have no idea how to create it on line.
All of my document configuration control experience was with an IT guy who set up the site and document location. Haven't a clue how to do that part myself. Once it is in place we will need someone to "own" it so changes are submitted and discussed here (in the thread) and only one person controls putting the changes in. If anyone can make changes to the document it gets out of control really fast and the process falls apart. My early experience with document configuration control taught me you can have more than one person putting stuff in, but only ONE person should control "write access".
Hank
Well I can do that (I do the Technical Resources page of the Foundation website). In fact I can see our new document including (or cross-referencing) a lot of the information already on that page.
Whether the Foundation wants it in their site is another matter...Forrest?
OK Robert...you seem to be way more up on making it web page accessible. May I suggest that we keep it in .pdf format? That’s an easy format to download and print out.
Actually if the master is saved in Word for those authorized to make the entries and then saved to the site for open access in pdf, the maintainers could make the changes and those downloading could print, but not change it. It is easy to save a Word file to pdf.
A system we use for "living" documents is to put the date at the end of the title so anyone with a printed copy can see quickly if they have the latest version.
The title would then look like;
Of course the date to which you refer Hank is a Spoonerism, but having worked in both the US (month first) and The Rest Of The World (day first), I prefer to use the ICAO, NASA and general wordly-acceptable protocol polite date convention which is YYYYMMDDMMSS etc.
Or at least using MMM for month, so that Jan is 01, etc, so that there is no confusion.
This missive is posted 201010121845...or in other (USA) language, 22OCT2010 at 18:45 ZULU
Comment