# Accident 20030308008249A: Fokker F27MK500, Kinston, NC, March 8, 2003 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: March 8, 2003, 10:27 local time - Place: Kinston, NC - Airport: Eastern Regional Jetport At Stall - Damage: Substantial damage - Phase of flight: Level Off Touchdown - Operating rules: Air carrier (Part 121) - Operator: MTNA - Location: 35.3281° N, 77.6153° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=35.3281&lon=-77.6153&mi=10 - Aircraft: N712FE, a cancelled registration (https://openairdocs.org/deregistered/N712FE-2005-03-14) (OpenAirDocs) - Registry model: Fokker F.27MK 500 (registry code 4990629, https://openairdocs.org/model/fokker-f-27mk-500) (OpenAirDocs) - Registry engine: Rolls-Royce DART532 series (registry code 54509, https://openairdocs.org/engine/rolls-royce-dart532-series) (OpenAirDocs) - Reported make and model: FOKKER F27MK500 - People aboard: 2 - Fatal injuries: 0 - Pilot flight hours: 8,130 total, 1,450 in this make and model, 78 in the last 90 days - NTSB investigation: [NTSB ATL03LA056](https://openairdocs.org/ntsb/ATL03LA056) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20030308008249A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) INSPECTOR STATEMENT: ON 03-08-2003 I WAS NOTIFIED BY FAA COM CENTER OF AN INCIDENT/ACCIDENT IN KINSTON NORTH CAROLINA. THE ACCIDENT INVOLVED A FOKKER F-27 N712FE THAT HAD RUN OFF THE SIDE OF RWY #5. THE AIRCRAFT WAS OPERATED BY MOUNTAIN AIR CARGO (MTNA) A 121 SUPPLEMENTAL CARRIER. THERE WERE NO INJURIES AND THE AIRCRAFT WAS SITTING OFF THE SIDE OF THE RUNWAY. THE AIRPORT WAS CLOSED. PRELIMINARY INFORMATION ON THE ACCIDENT WAS THAT THE RIGHT HAND MAIN GEAR HAD COLLAPSEDON LANDING WITH THE AIRCRAFT EXITING THE RUNWAY ACROSS TAXIWAY A-3 COMING TO REST BETWEEN THE RUNWAY AND TAXIWAY. REFERENCE: ATTACHMENT #1. MR. PHIL POWELL OF THE NTSB WAS CONFERENCED IN ON THE PHONE CALL. I INFORMED MR. POWELL THAT I WOULD CONTACT THE NECESSARY PEOPLE TO DETERMINE IF THE AIRCRAFT HAD RECEIVED SUBSTANTIAL DAMAGE AND COULD BE CATEGORIZED AS AN ACCIDENT. I CONTACTED THE KINSTON TOWER AND SPOKE TO A CONTROLLER NAMED GEAN AT 252-522-4844. GEAN INDICATED THAT EMERGENCY PERSONNEL WERE ON THE SCENE. GEAN INFORMED ME THAT THE AIRPORT MANAGER WAS IN RALEIGH ON THE WAY BACK TO KINSTON. THE CONTROLLER INDICATED THAT THE AIRPORT WAS CLOSED, BUT WITHIN AN HOUR WOULD OPEN BACK UP WITH ONE RUNWAY OPEN. I REQUESTED THAT GEAN INFORM THE EMERGENCY PERSONNEL ON SCENE NOT TO MOVE THE AIRCRAFT UNTIL I ARRIVED. GEAN AGREED TO THIS. I NEXT CONTACTED MOUNTAIN AIR CARGO (MAC) AND SPOKE TO THE DIRECTOR OF OPERATIONS MR. SAM STREET AND MR .BILL SIMPSON PRESIDENT OF MOUNTAIN AIR CARGO. MR. SAM STREET INFORMED ME THAT THE AIRCRAFT HAD LEFT GREENSBORO, NC EN ROUTE TO NEW BERN, NC. THE AIRCRAFT WAS MAKING ITS APPROACH INTO NEW BERN WHEN THE PILOTS NOTED A RIGHT HAND GEAR UNSAFE LIGHT. THE FLIGHT CREW DISCONTINUED THE APPROACH AND CONTACTED MAC. MAC ADVISED THAT THE CREW BURN OFF EXCESS FUEL, FOLLOW THE EMERGENCY PROCEDURES MANUAL, AND FLY THE AIRCRAFT TO KINSTON, NC FOR AN EMERGENCY LANDING. KINSTON, NC IS MAC'S MAIN MAINTENANCE BASE. MAC CONTACTED THE KINSTON TOWER AND INFORMED THE TOWER OF THE EMERGENCY LANDING. AFTER TALKING TO COMPANY PERSONNEL IT WAS DETERMINED THAT THE AIRCRAFT OCCURRENCE WOULD BE CATEGORIZED AS AN ACCIDENT DUE TO THE STRUCTURAL DAMAGE TO THE WING AND NOSE OF THE AIRCRAFT. I INFORMED THE MOUNTAIN AIR CARGO PERSONNEL NOT TO MOVE THE AIRCRAFT UNTIL I ARRIVED ON SCENE, AND THAT I WOULD NEED WRITTEN STATEMENTS FROM BOTH CREWMEMBERS. COM CENTER WAS CONTACTED AND INFORMED THAT I WAS GOING TO KINSTON TO PERFORM AN ACCIDENT INVESTIGATION. I ARRIVED AT THE ACCIDENT SCENE AT 1630 LOCAL. PHOTOS WERE TAKEN OF THE TOUCH DOWN POINT ON THE RUNWAY, AIRCRAFT PATH, AND THE ACCIDENT SCENE. I SPOKE TO THE FLIGHT CREW AND RECEIVED THEIR WRITTEN STATEMENTS. I RELEASED THE AIRCRAFT TO BE MOVED TO THE HANGAR TO DETERMINE WHAT FAILED IN THE LANDING GEAR SYSTEM TO CAUSE THE ACCIDENT. ON 03-09-2003 THE AIRCRAFT WAS PUT ON AIRCRAFT JACKS AND A NEW DRAG STRUT INSTALLED. THE GEAR WAS OPERATED UP AND DOWN WITH NO AIR LEAKS NOTED. I NEXT REVIEWED THE LANDING GEAR CONTROL SYSTEM IN THE FOKKER TECH DATA. DUE TO THE NATURE OF THE FAILURE JUST EFFECTING THE RIGHT GEARS SYSTEM AND NOT THE LEFT OR NOSE, THE SYSTEM WAS SEGREGATED AND ANALYZED. AIR PRESSURE TO THE RIGHT HAND GEAR SYSTEM WAS RULED OUT. PRESSURE CHECKED GOOD. THE RAM/ACTUATOR WAS REMOVED AND DISASSEMBLED WITH NO ABNORMALITIES NOTED. THE RAM/ACTUATOR INTERNAL SNUBBER VALVE FOR GEAR FREE FALL WAS DISASSEMBLED AND INSPECTED WITH NO ABNORMALITIES NOTED. THE SWIVEL LINES TO THE RAM/ACTUATOR WERE INSPECTED WITH NO ABNORMALITIES NOTED. THE EMERGENCY GEAR EXTENSION SHUTTLE VALVE WAS REMOVED AND INSPECTED WITH NO ABNORMALITIES NOTED. THE EMERGENCY EXTENSION HANDLE ACTUATION WAS INSPECTED WITH NO ABNORMALITIES NOTED. THE AIR SUPPLY TO THE SYSTEM WAS INSPECTED WITH NO CONTAMINATION NOTED. THE LOCK STRUT WAS INSPECTED WITH NO ABNORMALITIES NOTED. THE DRAG STRUT BREAK POINT WAS INITIALLY THOUGHT TO HAVE BEEN CAUSED BY THE FAILURE OF THE RAM OR EMERGENCY SYSTEM, BUT WAS REFOCUSED ON WITH ALL OTHER PORTIONS OF THE SYSTEM CHECKING GOOD. THE DRAG STRUT BREAK POINT WAS INSPECTED, NO BEACH MARKS WERE NOTED IN THE CRACK AREA, BUT THE DRAG STRUT FAILURE POINT AND METAL TEAR AND SHEAR POINTS INDICATED THAT THE DRAG STRUT FAILED FROM BEING PULLED UP BY THE RAM/ACTUATOR. THE MAIN GEAR FRONT DOOR THAT IS ATTACHED TO THE TOP OF THE DRAG STRUT WAS NOTED AS BEING BENT FORWARD NOT BACKWARD IN THE DIRECTION OF IMPACT. THE FAILED DRAG STRUT WAS REINSTALLED AND THE BENT MAIN GEAR FRONT DOOR BEND ALIGNED WITH THE FAILED DRAG STRUT. WITH THE DRAG STRUT AND THE MAIN GEAR FRONT DOOR ALIGNED IT SHOWED THAT THE DRAG STRUT HAD INITIALLY FAILED BEING PULLED UP INTO THE GEAR WHEEL WELL, DAMAGING THE LOCK STRUT MICRO SWITCH WHICH IN TURN CAUSED THE GEAR UNSAFE LIGHT. REFERENCE ATTACHMENT #2 AND #3. WITH THE AFOREMENTIONED ESTABLISHED A TECH DATA EVALUATION WAS PERFORMED REVEALING A DOWTY ROTOL SERVICE BULLETIN 32-42S DATED 8-28-1981 AND A CAA, AD/F27/104 ON THE SUBJECT. MAC PERSONNEL WERE TOLD TO QUARANTINE THE BROKEN DRAG STRUT UNTIL THE NTSB WAS CONTACTED TO SEE IF THEY WANTED THE DRAG STRUT TO GO TO THEIR LAB FOR TESTING. THE NTSB WAS CONTACTED ON 03-10-2003 AND UPDATED. ON 03-11-2003 THE NTSB REQUESTED THAT THE DRAG STRUT BE SENT TO THE NTSB FOR ANALYSIS. MAC WAS CONTACTED AND GIVEN THE NTSB ADDRESS OF WHERE TO SEND THE DRAG STRUT. THE FOLLOWING ITEMS WERE FAXED TO THE NTSB FOR REVIEW. A. ISIS AIRMEN REPORT B. PILOT WRITTEN STATEMENTS C. CREWMEMBER DATA SHEETS D. CAA AD/F27/104 E. DOWTY ROTOL SERVICE BULLETIN 34-42S. PENDING THE NTSB LAB REPORT A SAFETY RECOMMENDATION WILL BE DRAFTED AND SENT TO WASHINGTON SUGGESTING A REPETITIVE NDT INSPECTION ON THE DRAG STRUT, IN LIEU OF THE ONE-TIME INSPECTION NOTED IN THE DOWTY ROTOL SERVICE BULLETIN. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB ATL03LA056](https://openairdocs.org/ntsb/ATL03LA056), Mar 8, 2003: Fokker F.27MK 500 (N712FE), Kinston, NC, substantial damage. Probable cause: The fatigue failure of the main drag stay tube. A factor is no inspection procedure required. ## Other reports on N712FE (2) Matched to the same aircraft by N-number and date. - [Incident 20010524012679I](https://openairdocs.org/incident/20010524012679I), May 24, 2001: Fokker F27MK500 (N712FE), Indianapolis, IN. (-23) On 05/24/01, mountain air cargo (mtna), F-27-MK500 aircraft registration N712FE, operating under flight 8201 inbound to ind from bna, declared an… - [Incident 19930324022259I](https://openairdocs.org/incident/19930324022259I), Mar 24, 1993: Fokker F27MK500 (N712FE), Atlanta, GA, Minor damage. Left engine fire light after takeoff. Fired fire bottles. Engine secured. Returned. Landed safely. 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.