37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 380828 |
Time | |
Date | 199709 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : osu |
State Reference | OH |
Altitude | msl bound lower : 2000 msl bound upper : 2000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : osu |
Operator | general aviation : corporate |
Make Model Name | Beechjet 400 |
Operating Under FAR Part | Part 91 |
Navigation In Use | Other Other |
Flight Phase | descent : approach landing : go around |
Route In Use | approach : visual arrival other |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise other |
Flight Plan | VFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : atp pilot : cfi |
Experience | flight time last 90 days : 130 flight time total : 3700 flight time type : 170 |
ASRS Report | 380828 |
Person 2 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : nmac non adherence : far other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
Resolutory Action | flight crew : took evasive action other |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 0 vertical : 100 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Pilot Deviation Operational Deviation |
Narrative:
We were on an IFR flight plan from pbi to osu, departing pbi at XA00. We were cleared for a visual approach to runway 27L at osu by osu approach control and told to contact the osu tower. The PNF switched to osu tower frequency and reported 10 mi east of the airport for runway 27L. Osu tower told us to identify and report a 4 mi final. We confirmed. While descending out of 2200 ft MSL, about 4 mi from the runway, we received a TA on our TCASII. Approximately 4 seconds later we received a 'climb, climb, climb' command from our TCASII. I immediately climbed the aircraft and the PNF saw a C172 pass approximately 100 ft below us. We had heard the cessna report his position northeast to osu tower and were aware there could be a possible conflict. The tower was not situationally aware of either aircraft's position. We reported a near miss to the tower and continued our approach. While again descending to the runway we noticed a low wing aircraft landing on runway 9R after we were cleared to land on runway 27L. We initiated a go around, made left traffic and landed on runway 27L. The osu tower has recently switched from an FAA tower to a contract tower. I feel they have not been prepared fully to handle the multiplicity of osu's traffic. I have spoken with/overheard other pilots on the field and most feel that the 'new' tower has jeopardized safety. Callback conversation with reporter revealed the following information: reporter first officer is quite experienced in the osu area and airport. Having graduated from osu and working there for 6 yrs as an instructor pilot, he knows that facility's operations extremely well. He stated that this past summer the tower went to a contracted tower status. He does not know the managing company or the mgrs by name. He did meet the controllers after said incident took place. He lives near the airport and can watch traffic from his home. He has seen 'many' strange occurrences lately, those of near misses, aircraft trying to avoid each other. Generally, as he says, 'bedlam.' he was not impressed with the demeanor or attitude of the controllers he spoke with. They were very unprofessional and were making what he termed as 'lame' excuses for the 2 incidents that affected his flight. In speaking with other pilots flying in and out of osu, he found that all the others agreed with him on the sad situation in air traffic control at osu. Seems there is no one in charge, with the tower controller's performance indicating a lack of proficiency. He would really like to see some contact with managerial staff, whoever that might be, and effective training instituted.
Original NASA ASRS Text
Title: CPR FLC IN A BEECH JET 400A EXPERIENCE AN NMAC ON A 4 MI FINAL TO OSU RWY 27L, A XING C172 AT THEIR ALT. THE C172 HAD GIVEN A POS RPT TO CONTRACT TWR, JUST PRIOR TO THE BE40'S ARRIVING AT THE 4 DME FINAL. AFTER THE TCASII RA AND EVASIVE ACTION, THE BE40 WAS CLRED TO LAND BUT CREW THEN NOTED AN SMA LNDG OPPOSITE DIRECTION ON RWY 9R. THE BE40 FLC WENT AROUND. FO CITES POOR CTLR PERCEPTION CREATING DANGEROUS SITS.
Narrative: WE WERE ON AN IFR FLT PLAN FROM PBI TO OSU, DEPARTING PBI AT XA00. WE WERE CLRED FOR A VISUAL APCH TO RWY 27L AT OSU BY OSU APCH CTL AND TOLD TO CONTACT THE OSU TWR. THE PNF SWITCHED TO OSU TWR FREQ AND RPTED 10 MI E OF THE ARPT FOR RWY 27L. OSU TWR TOLD US TO IDENT AND RPT A 4 MI FINAL. WE CONFIRMED. WHILE DSNDING OUT OF 2200 FT MSL, ABOUT 4 MI FROM THE RWY, WE RECEIVED A TA ON OUR TCASII. APPROX 4 SECONDS LATER WE RECEIVED A 'CLB, CLB, CLB' COMMAND FROM OUR TCASII. I IMMEDIATELY CLBED THE ACFT AND THE PNF SAW A C172 PASS APPROX 100 FT BELOW US. WE HAD HEARD THE CESSNA RPT HIS POS NE TO OSU TWR AND WERE AWARE THERE COULD BE A POSSIBLE CONFLICT. THE TWR WAS NOT SITUATIONALLY AWARE OF EITHER ACFT'S POS. WE RPTED A NEAR MISS TO THE TWR AND CONTINUED OUR APCH. WHILE AGAIN DSNDING TO THE RWY WE NOTICED A LOW WING ACFT LNDG ON RWY 9R AFTER WE WERE CLRED TO LAND ON RWY 27L. WE INITIATED A GAR, MADE L TFC AND LANDED ON RWY 27L. THE OSU TWR HAS RECENTLY SWITCHED FROM AN FAA TWR TO A CONTRACT TWR. I FEEL THEY HAVE NOT BEEN PREPARED FULLY TO HANDLE THE MULTIPLICITY OF OSU'S TFC. I HAVE SPOKEN WITH/OVERHEARD OTHER PLTS ON THE FIELD AND MOST FEEL THAT THE 'NEW' TWR HAS JEOPARDIZED SAFETY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR FO IS QUITE EXPERIENCED IN THE OSU AREA AND ARPT. HAVING GRADUATED FROM OSU AND WORKING THERE FOR 6 YRS AS AN INSTRUCTOR PLT, HE KNOWS THAT FACILITY'S OPS EXTREMELY WELL. HE STATED THAT THIS PAST SUMMER THE TWR WENT TO A CONTRACTED TWR STATUS. HE DOES NOT KNOW THE MANAGING COMPANY OR THE MGRS BY NAME. HE DID MEET THE CTLRS AFTER SAID INCIDENT TOOK PLACE. HE LIVES NEAR THE ARPT AND CAN WATCH TFC FROM HIS HOME. HE HAS SEEN 'MANY' STRANGE OCCURRENCES LATELY, THOSE OF NEAR MISSES, ACFT TRYING TO AVOID EACH OTHER. GENERALLY, AS HE SAYS, 'BEDLAM.' HE WAS NOT IMPRESSED WITH THE DEMEANOR OR ATTITUDE OF THE CTLRS HE SPOKE WITH. THEY WERE VERY UNPROFESSIONAL AND WERE MAKING WHAT HE TERMED AS 'LAME' EXCUSES FOR THE 2 INCIDENTS THAT AFFECTED HIS FLT. IN SPEAKING WITH OTHER PLTS FLYING IN AND OUT OF OSU, HE FOUND THAT ALL THE OTHERS AGREED WITH HIM ON THE SAD SIT IN AIR TFC CTL AT OSU. SEEMS THERE IS NO ONE IN CHARGE, WITH THE TWR CTLR'S PERFORMANCE INDICATING A LACK OF PROFICIENCY. HE WOULD REALLY LIKE TO SEE SOME CONTACT WITH MANAGERIAL STAFF, WHOEVER THAT MIGHT BE, AND EFFECTIVE TRAINING INSTITUTED.
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.