37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 287901 |
Time | |
Date | 199411 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : sju |
State Reference | PR |
Altitude | msl bound lower : 4000 msl bound upper : 4000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air taxi |
Make Model Name | DC-3/Dakota/Skytrain |
Operating Under FAR Part | Part 135 |
Flight Phase | cruise other other |
Route In Use | arrival : on vectors enroute : on vectors enroute airway : sju |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 5000 |
ASRS Report | 287901 |
Person 2 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : required legal separation non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : declared emergency other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation |
Narrative:
I was flying a dc-3 on an airway, 40 west of san juan. IFR flight plan, but VFR conditions, was level at 4000 ft. Appeared to have a rough running engine and did a magneto check in the air and identify the right engine as the problem. Wasn't a serious problem and believed I might be able to complete the flight safely. However, engine started to run rougher and at that time the other engine, which was running normally up to that time, started to miss badly. Reduced power on both engines and did an immediate 180 to return directly to san juan. Maintained 4000 ft. Advised ATC of the turn back and ATC directed me to a heading of 020 degrees and descend to 3000 ft. I advised them that I had a problem and that I was unable their heading and altitude change. Told them it was imperative that I hold a direct heading back to the airport and that I maintain my altitude of 4000 ft until I was close in to the airport. I proceeded straight in to the airport and descended to pattern altitude close in and made a normal landing. On a number of occasions, I was asked by ATC to change headings/altitudes, but wasn't able to comply. Did not declare an emergency at that time because the engines seemed to run satisfactorily at reduced power -- the aircraft carried no cargo on that flight. However, crash fire was present on touchdown and escorted the aircraft back to parting -- was told later that my radar blip merged on the radar screen with another's blip, but ATC never advised me that we were in close proximity with another aircraft. I was criticized for not declaring an emergency and that's constructive and believe I will from now on. As for the aircraft with malfunctioning engines. I believe the FAA should monitor all aviation operations in puerto rico much more closely to ensure good maintenance is being performed.
Original NASA ASRS Text
Title: RETURN LAND DUE TO 2 ROUGH RUNNING ENGS.
Narrative: I WAS FLYING A DC-3 ON AN AIRWAY, 40 W OF SAN JUAN. IFR FLT PLAN, BUT VFR CONDITIONS, WAS LEVEL AT 4000 FT. APPEARED TO HAVE A ROUGH RUNNING ENG AND DID A MAGNETO CHK IN THE AIR AND IDENT THE R ENG AS THE PROB. WASN'T A SERIOUS PROB AND BELIEVED I MIGHT BE ABLE TO COMPLETE THE FLT SAFELY. HOWEVER, ENG STARTED TO RUN ROUGHER AND AT THAT TIME THE OTHER ENG, WHICH WAS RUNNING NORMALLY UP TO THAT TIME, STARTED TO MISS BADLY. REDUCED PWR ON BOTH ENGS AND DID AN IMMEDIATE 180 TO RETURN DIRECTLY TO SAN JUAN. MAINTAINED 4000 FT. ADVISED ATC OF THE TURN BACK AND ATC DIRECTED ME TO A HDG OF 020 DEGS AND DSND TO 3000 FT. I ADVISED THEM THAT I HAD A PROB AND THAT I WAS UNABLE THEIR HDG AND ALT CHANGE. TOLD THEM IT WAS IMPERATIVE THAT I HOLD A DIRECT HDG BACK TO THE ARPT AND THAT I MAINTAIN MY ALT OF 4000 FT UNTIL I WAS CLOSE IN TO THE ARPT. I PROCEEDED STRAIGHT IN TO THE ARPT AND DSNDED TO PATTERN ALT CLOSE IN AND MADE A NORMAL LNDG. ON A NUMBER OF OCCASIONS, I WAS ASKED BY ATC TO CHANGE HDGS/ALTS, BUT WASN'T ABLE TO COMPLY. DID NOT DECLARE AN EMER AT THAT TIME BECAUSE THE ENGS SEEMED TO RUN SATISFACTORILY AT REDUCED PWR -- THE ACFT CARRIED NO CARGO ON THAT FLT. HOWEVER, CRASH FIRE WAS PRESENT ON TOUCHDOWN AND ESCORTED THE ACFT BACK TO PARTING -- WAS TOLD LATER THAT MY RADAR BLIP MERGED ON THE RADAR SCREEN WITH ANOTHER'S BLIP, BUT ATC NEVER ADVISED ME THAT WE WERE IN CLOSE PROX WITH ANOTHER ACFT. I WAS CRITICIZED FOR NOT DECLARING AN EMER AND THAT'S CONSTRUCTIVE AND BELIEVE I WILL FROM NOW ON. AS FOR THE ACFT WITH MALFUNCTIONING ENGS. I BELIEVE THE FAA SHOULD MONITOR ALL AVIATION OPS IN PUERTO RICO MUCH MORE CLOSELY TO ENSURE GOOD MAINT IS BEING PERFORMED.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.