OpenAirDocs.org

20140506008939I

Incident · No damage
Open the Markdown

FAA incident report · Hawker Siddeley BH.125-400A · Fort Lauderdale, FL · May 6, 2014

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
May 6, 2014 · 13:30 local
Place
Fort Lauderdale, FL
Phase of flight
Takeoff: Departure Roll
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N800NP
Reported as
Hawker Siddeley BH.125-400A
Reported engine
Honeywell TFE-731
People aboard
9
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Commercial pilot
Pilot’s flight hours
5,400 total3,500 in this make and model65 in the last 90 days
N800NPRegistration cancelled Jun 19, 2015 · Hawker Siddeley BH.125-400AS/N NA.758 · Built 1970Airframe modelHawker Siddeley BH.125-400AEngine modelRolls-Royce VIPER MK522Turbo-jet

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

On may 6, 2014, approximately 1330 hours a Hawker Siddeley, model number bh.125-400A, registration number N800NP, serial number 758, was preparing for departure from Fort Lauderdale airport(kfll) with a planned destination to caracas, venezuela, airport(svcs). The aircraft was piloted by privacy data omitted, certificate number privacy data omitted, a free-lance pilot with a commercial pilot rating hired by the president of ajs Hawker inc., the registered owner of the aircraft. The pilot stated after all items on the checklist were cleared they proceeded with the normal take-off procedure from runway 10L. A few seconds after this the engine computer light for engine number 1, came on and following the aircraft procedures the pilot aborted take-off. After exiting the active runway the pilot made a request to ground control to allow him some time to check his aircraft which he did and was able to bring the engine computer back on line. The pilot then checked all associated items with the engine computer and noting normal operation he then asked ground control if the IFR flight plan was still active in order to proceed with the planned flight. The aircraft was cleared to taxi up and hold off 10L, after receiving the standard briefing the pilot proceeded with the take-off maneuver and climbed to an altitude approximately 11000-12000 feet on initial climb, at that time the left engine computer went off line. The pilot stated they followed the aircraft procedures and decided to turn back to Fort Lauderdale, the pilot contacted air traffic controllers (ATC) and reported their situation and they were not declaring an emergency and did not need to expedite turns to the airport. The aircraft was then cleared to position dekal for the arrival into the airport and received radar vector to ILS runway 10L where the aircraft made an uneventful landing. After landing the pilot reported the events of the flight to the awaiting mechanics that was being directed Florida jet solutions, LLC, at sheltair, who reportedly, manage the aircraft.

As the FAA filed it

ON MAY 6, 2014, APPROXIMATELY 1330 HOURS A HAWKER SIDDELEY, MODEL NUMBER BH.125-400A, REGISTRATION NUMBER N800NP, SERIAL NUMBER 758, WAS PREPARING FOR DEPARTURE FROM FORT LAUDERDALE AIRPORT(KFLL) WITH A PLANNED DESTINATION TO CARACAS, VENEZUELA, AIRPORT(SVCS). THE AIRCRAFT WAS PILOTED BY ^PRIVACY DATA OMITTED^, CERTIFICATE NUMBER ^PRIVACY DATA OMITTED^, A FREE-LANCE PILOT WITH A COMMERCIAL PILOT RATING HIRED BY THE PRESIDENT OF AJS HAWKER INC., THE REGISTERED OWNER OF THE AIRCRAFT. THE PILOT STATED AFTER ALL ITEMS ON THE CHECKLIST WERE CLEARED THEY PROCEEDED WITH THE NORMAL TAKE-OFF PROCEDURE FROM RUNWAY 10L. A FEW SECONDS AFTER THIS THE ENGINE COMPUTER LIGHT FOR ENGINE NUMBER 1, CAME ON AND FOLLOWING THE AIRCRAFT PROCEDURES THE PILOT ABORTED TAKE-OFF. AFTER EXITING THE ACTIVE RUNWAY THE PILOT MADE A REQUEST TO GROUND CONTROL TO ALLOW HIM SOME TIME TO CHECK HIS AIRCRAFT WHICH HE DID AND WAS ABLE TO BRING THE ENGINE COMPUTER BACK ON LINE. THE PILOT THEN CHECKED ALL ASSOCIATED ITEMS WITH THE ENGINE COMPUTER AND NOTING NORMAL OPERATION HE THEN ASKED GROUND CONTROL IF THE IFR FLIGHT PLAN WAS STILL ACTIVE IN ORDER TO PROCEED WITH THE PLANNED FLIGHT. THE AIRCRAFT WAS CLEARED TO TAXI UP AND HOLD OFF 10L, AFTER RECEIVING THE STANDARD BRIEFING THE PILOT PROCEEDED WITH THE TAKE-OFF MANEUVER AND CLIMBED TO AN ALTITUDE APPROXIMATELY 11000-12000 FEET ON INITIAL CLIMB, AT THAT TIME THE LEFT ENGINE COMPUTER WENT OFF LINE. THE PILOT STATED THEY FOLLOWED THE AIRCRAFT PROCEDURES AND DECIDED TO TURN BACK TO FORT LAUDERDALE, THE PILOT CONTACTED AIR TRAFFIC CONTROLLERS (ATC) AND REPORTED THEIR SITUATION AND THEY WERE NOT DECLARING AN EMERGENCY AND DID NOT NEED TO EXPEDITE TURNS TO THE AIRPORT. THE AIRCRAFT WAS THEN CLEARED TO POSITION DEKAL FOR THE ARRIVAL INTO THE AIRPORT AND RECEIVED RADAR VECTOR TO ILS RUNWAY 10L WHERE THE AIRCRAFT MADE AN UNEVENTFUL LANDING. AFTER LANDING THE PILOT REPORTED THE EVENTS OF THE FLIGHT TO THE AWAITING MECHANICS THAT WAS BEING DIRECTED FLORIDA JET SOLUTIONS, LLC, AT SHELTAIR, WHO REPORTEDLY, MANAGE THE AIRCRAFT.