I am also interested on FAR 23 Loads Professional Program 2003
Only I found the user manual only in FAA page.
Any link for download the program please?
Hi, The software was purchased by Michael McGettrick and he will not release the latest version. He can be contacted on Michael McGettrick [michael@mcgettrickengineering.com].
My company purchased the original Hal MacMaster version and have been very pleased with it. The FAA conducted some validation work and found no reason to change the code. We did the same (against a single engine turboprop, retractable, taper wing aircraft) and found a number of outdated or incorrect parameters. I still have the validation report for that project to hand and the FAA validation report.
Michael McGettrick wants to gage the demand for such a program, so the more people intrested the better chance there is of getting the latest version on to the market.
The original version is very useable but is not integrated, much input has to be repeated for the next module. However, it sure be is better than doing it manually.
I bought also the Mc Master software. It is good soft keeping in mind was made in Basic .But due FAA made a few FAR 23 modification I am looking for an updated code.
I think the only way is modifying the Mc Master code according
FAA FAR 23 new requirements. I strongly agree with your sentence: "The original version is very usable but is not integrated, much input has to be repeated for the next module. However, it sure be is better than doing it manually".
This is Mike McGettrick, and I was directed to this thread by a user of my program FAR23 Loads. I would like to add a little background to clear up some information that I get occasionally. I own the copyright, and purchased from the original author, Hal McMaster, who was no longer able to support it.
The FAA does not have the authority to distribute the program by signed agreement with Hal McMaster, but can use it internally.
The 2003 version contains many enhancements recommended by the FAA, and now has a single input file, rather than one for each module. The modules all share a common database, and therefore one does not need to enter the same data multiple times. I would like to release the software, but it has a lot of bugs to be resolved. It also does not have any type of security built in to keep it from being distributed. Therefore I have chosen not to release it. It is a side project for me, and while I can do the calculation type programming I do not have the experience to do the interface type of bugs easily.
I also know that some companies have used the basic code to create their own code. This is ok, as long as the company does not use more than one copy, or does not sell copies. This would violate the copyright restrictions.
I am sorry that it has taken me so long to get the next release out, but it is expensive to complete. I thought I was going to get a COOP for the summer, but have not had any interest. I have not forgotten about the program. I also know that there are not thousands of buyers as there are with many programs, more like 100 or less that would be willing to pay what it will take to develop and maintain the software.
Looks like I better find that floppy, I obtained it back when the code was still public domain (prior to being copyrighted). Me & Jed are gonna be millionaires!
Seriously, I would be a potential buyer. Having it ported to a nice VisualBASIC GUI, bugs resolved, and more recent parameters incorporated is a problem worth $500 to me. And that is not based on finding an Apple IIe or 386 PC, or whatever it was back when I ran the program (which was most recently a decade ago - so not a pressing problem - been using other tools since). I myself have no interest whatsoever in dealing with such issues either, gotten quite comfortable with modern computing resources, but only as a user. So Mike - hopefully this is one data point in your decision to develop or not. I can also suggest offshoring the effort, which would solve your lack of a coop and more than likely be more affordable. Or else maybe consider directly approaching a college CS department as a student project.
der8110, the program was never in public domain. Hal McMaster copyrighted his program from the first release. If the ACO gave you a copy, they did so in violation of their agreement, and copyright laws. Back in the earlier days of computer programming, sharing of copyrighted material was quite common, but still in violation of copyright laws.
I have had a COOP from the local university, but the last one left and have not had any interest. I am reluctant to send the source code to another country for the same concerns.
The program is 95% complete. I will spend some time today to send out more inquiries as to who might be able to help.
I was mistaken; the program I referred to was basically a coded version of AFS-120-73-2, developed by two FAA employees on FAA time (thus I said public domain), one of whom gave it to me when he was working at the Small Airplane Directorate. This would have been early '90's.
Now had I seen DOT/FAA/AR-96/46, then I would have realized this is an external loads program not fatigue loads. Now I definitely want it! (but sure would like the AFS-120-73-2 program updated)
Sorry about the confusion, and no worries about the copyright.
I do not know what FAR23Owner paid to obtain the copyrights to the program, or how much he has invested in it, but my suggestion would be to release the program to public domain as was done with Unix and Linux. This allows new input into the program to maybe make it a more robust program and allowing company specific tayloring.
This is not an ideal situation, especially for FAR23Owner, who I am sure has invested time and money into this program, but by not completing the work in a timely fashion, risks it never getting released due to FAR updates over the years. Eventually, the existance of this program will fade and disappear just as so much knowledge has in the name of copyright protection.
Please do not view this as a criticism of FAR23Owner or the copyright laws, he is entitled to the rewards of his hard work. However, copyright rights should be released if their activity associated with it wanes in the interest of progress.
