# Incident 20140506008939I: Hawker Siddeley BH.125-400A, Fort Lauderdale, FL, May 6, 2014

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 6, 2014, 13:30 local time
- Place: Fort Lauderdale, FL
- Damage: No damage
- Phase of flight: Takeoff: Departure Roll
- Operating rules: General operating rules (Part 91)
- Location: 26.1223° N, 80.1434° W: Placed by OpenAirDocs: center of Fort Lauderdale, FL, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=26.1223&lon=-80.1434&mi=10
- Aircraft: N800NP, a cancelled registration (https://openairdocs.org/deregistered/N800NP-2015-06-19) (OpenAirDocs)
- Registry model: Hawker Siddeley BH.125-400A (registry code 4230138, https://openairdocs.org/model/hawker-siddeley-bh-125-400a) (OpenAirDocs)
- Registry engine: Rolls-Royce VIPER MK522 (registry code 54552, https://openairdocs.org/engine/rolls-royce-viper-mk522) (OpenAirDocs)
- Reported make and model: HAWKER SIDDELEY BH.125-400A
- Reported engine: HONEYWELL TFE 731
- People aboard: 9
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 5,400 total, 3,500 in this make and model, 65 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20140506008939I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

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.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.