37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 435311 |
Time | |
Date | 199904 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : luk.airport |
State Reference | OH |
Altitude | msl single value : 1600 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : luk.tower |
Operator | general aviation : corporate |
Make Model Name | Challenger CL600 |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : multi engine pilot : atp pilot : commercial |
Experience | flight time last 90 days : 75 flight time total : 14320 flight time type : 3230 |
ASRS Report | 435311 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 90 flight time total : 4500 flight time type : 1900 |
ASRS Report | 435519 |
Events | |
Anomaly | non adherence : far |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were descending visually for a landing at luk airport. A large area of heavy rain and thunderstorms had previously moved across the airport and the WX seemed to be clearing rapidly behind it. We continued descent and as we came within 5-6 mi of the airport an area of low stratus clouds formed between us and the field preventing us from seeing the field. We began a right turn in an attempt to maintain a visual with the runway and continued descent. Turning further to the right we picked up the airport visually at which time the tower controller called us telling us we were too low and in the airspace of an adjacent field. At our 1 O'clock position and 2 mi was blue ash airport, which neither of us knew about. A normal approach and landing were executed from that point. No contact was ever attempted with the other control tower and, to our knowledge, no traffic conflicts existed. I personally placed an unsolicited call to the luk tower to explain why we flew the procedure. It was stressed that we maintained VFR the entire time and should have alerted them that we lost line of sight contact with the airport. As crew members we were both at the time never in doubt of acquiring visual with the airport but more concerned about staying well clear of the lower cloud deck. We were both concentrating our vision to the forward left side of the aircraft and did not notice the other field off our right front. Contributing factors: this was the second leg of the day (ewr-luk). The first (lex-ewr) began at XA00 that same morning and we were both less than well rested. Also we had just spent 1/2 hour negotiating our way through a very active frontal zone. Looking back, I would say from now on I should immediately relay to the controller anything nonstandard. They could have provided us with vectors or the ability to enter the other airport's airspace.
Original NASA ASRS Text
Title: A CHALLENGER 600 FLC, ON A VISUAL APCH TO LUK, FLEW THROUGH 22OH AIRSPACE WITHOUT CLRNC WHILE TRYING TO REMAIN CLR OF CLOUDS.
Narrative: WE WERE DSNDING VISUALLY FOR A LNDG AT LUK ARPT. A LARGE AREA OF HVY RAIN AND TSTMS HAD PREVIOUSLY MOVED ACROSS THE ARPT AND THE WX SEEMED TO BE CLRING RAPIDLY BEHIND IT. WE CONTINUED DSCNT AND AS WE CAME WITHIN 5-6 MI OF THE ARPT AN AREA OF LOW STRATUS CLOUDS FORMED BTWN US AND THE FIELD PREVENTING US FROM SEEING THE FIELD. WE BEGAN A R TURN IN AN ATTEMPT TO MAINTAIN A VISUAL WITH THE RWY AND CONTINUED DSCNT. TURNING FURTHER TO THE R WE PICKED UP THE ARPT VISUALLY AT WHICH TIME THE TWR CTLR CALLED US TELLING US WE WERE TOO LOW AND IN THE AIRSPACE OF AN ADJACENT FIELD. AT OUR 1 O'CLOCK POS AND 2 MI WAS BLUE ASH ARPT, WHICH NEITHER OF US KNEW ABOUT. A NORMAL APCH AND LNDG WERE EXECUTED FROM THAT POINT. NO CONTACT WAS EVER ATTEMPTED WITH THE OTHER CTL TWR AND, TO OUR KNOWLEDGE, NO TFC CONFLICTS EXISTED. I PERSONALLY PLACED AN UNSOLICITED CALL TO THE LUK TWR TO EXPLAIN WHY WE FLEW THE PROC. IT WAS STRESSED THAT WE MAINTAINED VFR THE ENTIRE TIME AND SHOULD HAVE ALERTED THEM THAT WE LOST LINE OF SIGHT CONTACT WITH THE ARPT. AS CREW MEMBERS WE WERE BOTH AT THE TIME NEVER IN DOUBT OF ACQUIRING VISUAL WITH THE ARPT BUT MORE CONCERNED ABOUT STAYING WELL CLR OF THE LOWER CLOUD DECK. WE WERE BOTH CONCENTRATING OUR VISION TO THE FORWARD L SIDE OF THE ACFT AND DID NOT NOTICE THE OTHER FIELD OFF OUR R FRONT. CONTRIBUTING FACTORS: THIS WAS THE SECOND LEG OF THE DAY (EWR-LUK). THE FIRST (LEX-EWR) BEGAN AT XA00 THAT SAME MORNING AND WE WERE BOTH LESS THAN WELL RESTED. ALSO WE HAD JUST SPENT 1/2 HR NEGOTIATING OUR WAY THROUGH A VERY ACTIVE FRONTAL ZONE. LOOKING BACK, I WOULD SAY FROM NOW ON I SHOULD IMMEDIATELY RELAY TO THE CTLR ANYTHING NONSTANDARD. THEY COULD HAVE PROVIDED US WITH VECTORS OR THE ABILITY TO ENTER THE OTHER ARPT'S AIRSPACE.
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.