Arabian Airlines - AUTOMATION HELP NEEDED

Over the past few months Arabian Airlines has been waiting patiently for an automation system that was promised to us by a third party that has recently abandoned us. At this point, Arabian Airlines finds itself in the middle of a potential crisis. Without an automation system, databases, PiRep and Roster Systems, etc., the airline cannot relaunch.Thus we come to this community to ask for assistance, and we are gladly willing to pay for it. We have a completed front end website (php), webspace, domain, and the ability to create SQL databases on our own server. We have until June to get this airline operational. We ask that any experienced coder who wishes to help this airline please email me at makiATasquaref.com. We ask that those interested please, if possible, give us examples of their work. Below is a list of what we are looking for.

Pilot database:The pilot database should store:- Name- Log-in name- password- hours flown- hours flown by type- rank- the log made up of his filed PIREPs- a map with the routes he's flown (great circle mapper)- present location- passengers carriedOther stats could also be included, such as average flight duration, hours per year, passengers per flight, or even flights per specific aircraft (in terms of registration).- The site should include a "staff-travel" facility, to change the location. Think of it as jump seating. It will not give credit to pilot.- When booking a flight, the pilot should be able to view the flights available from his present location at the present day- After booking, the pilot should be presented with a page giving him a variety of information regarding the flight. this info would include the following:- Departure/arrival airport in the format:Queen Alia Intl, Amman, Jordan - OJAI/AMM- Flight number as in:ARB/AN 0307- Departure and arrival times, both in UTC and local times.- Aircraft info, including type, registration, and seat configuration- Passenger load (Possibly a random number for each class, within some percentage boundaries?) Simple map (great circle)- PIREPs should be partly pre-completed.. this means that, flight number, departure, destination, and scheduled take off and arrival times, and passengers carried (per class, and total) should be pre-completedThe following should be completed by the pilot:- type (drop-down list)- registration (again drop-down list)- off block time- take off time- landing time- block on time- total time (in decimal)- fuel used- cruising flight level- cruising mach speed- departure/arrival runway- departure/arrival gate- SID/STAR- routing- commentsPIREPs should ALL be reviewed and approved by an administrator, before the hours are added to the account. Promotions should also all be reviewed before being granted.- Administrative interfaceThe administrators should easily be able to change all data regarding flights, pilots, and fleet.- Flights database for each flight store:- departure/arrival airport- flight number- aircraft type- registration- departure/arrival times (both UTC and LT)- durationNote that not all flights are offered every day, and each day the aircraft used is most probably differentOther than these, there should ideally be a facility to look through the timetable, or download it as a file.