37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 449524 |
Time | |
Date | 199909 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : luk.airport |
State Reference | OH |
Altitude | msl single value : 2400 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : luk.tower |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure : vfr |
Aircraft 2 | |
Operator | general aviation : personal |
Make Model Name | Cessna Aircraft Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 11 flight time total : 121.4 flight time type : 10.2 |
ASRS Report | 449524 |
Events | |
Anomaly | airspace violation : entry conflict : airborne less severe non adherence : published procedure non adherence : far non adherence : clearance non adherence : required legal separation |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : exited penetrated airspace flight crew : took evasive action flight crew : took precautionary avoidance action flight crew : became reoriented |
Miss Distance | horizontal : 200 vertical : 1000 |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I have 2 sits to report and both directly relate to cincinnati class B airspace. Issue #1 developed immediately after departing cincinnati lunken field. I departed on runway 21R and was instructed by lunken tower to make a departing right turn and proceed to the north. In order to give separation from traffic in the pattern, I wanted to climb above the traffic pattern altitude. Unfortunately there is not much space to do this to the west of the field. While watching for traffic, I inadvertently climbed to an altitude of 2400 ft MSL before taking corrective action to descend to 2100 ft. While I am quite sure, although not 100% sure, that I did not enter class B airspace by flying too far to the west, this event showed me how easily an incursion into the class B airspace could happen around lunken field. The class B airspace just 2 mi to the west of lunken field has a base of 2100 ft, while the base immediately surrounding lunken is 3500 ft. (The class D lunken airspace has 4 different base levels of class B airspace in it or above it). My plane was not outfitted with GPS, but I did have DME. Unfortunately, since the cvg VOR is not on the field, my DME was useless in this event. I recommend moving the VOR to the cvg field to better aid pilots in locating the boundaries of the class B airspace. The second issue concerns the suggested VFR flyways on the VFR terminal area chart for cincinnati. The northeast flying lines up perfectly with the parallel runways of lunken field. That means traffic in and out of the cincinnati area and lunken traffic is using the same airspace. Thanks to the lunken tower for keeping watch. They reported traffic to me at 12 O'clock position, and I had to take evasive action to avoid the incoming aircraft. This incident occurred on the outer rim of the class D airspace at approximately 2700 ft. My suggestion would be to move the northeast flyway so the lunken traffic isn't on the same course. Until these issues get corrected, I'm going to avoid lunken field.
Original NASA ASRS Text
Title: A PVT RATED PLT FLYING A C172 FROM LUK RPTS CONFUSION AND DIFFICULTY NAVING TO REMAIN CLR OF CLASS B AND CLASS D AIRSPACE.
Narrative: I HAVE 2 SITS TO RPT AND BOTH DIRECTLY RELATE TO CINCINNATI CLASS B AIRSPACE. ISSUE #1 DEVELOPED IMMEDIATELY AFTER DEPARTING CINCINNATI LUNKEN FIELD. I DEPARTED ON RWY 21R AND WAS INSTRUCTED BY LUNKEN TWR TO MAKE A DEPARTING R TURN AND PROCEED TO THE N. IN ORDER TO GIVE SEPARATION FROM TFC IN THE PATTERN, I WANTED TO CLB ABOVE THE TFC PATTERN ALT. UNFORTUNATELY THERE IS NOT MUCH SPACE TO DO THIS TO THE W OF THE FIELD. WHILE WATCHING FOR TFC, I INADVERTENTLY CLBED TO AN ALT OF 2400 FT MSL BEFORE TAKING CORRECTIVE ACTION TO DSND TO 2100 FT. WHILE I AM QUITE SURE, ALTHOUGH NOT 100% SURE, THAT I DID NOT ENTER CLASS B AIRSPACE BY FLYING TOO FAR TO THE W, THIS EVENT SHOWED ME HOW EASILY AN INCURSION INTO THE CLASS B AIRSPACE COULD HAPPEN AROUND LUNKEN FIELD. THE CLASS B AIRSPACE JUST 2 MI TO THE W OF LUNKEN FIELD HAS A BASE OF 2100 FT, WHILE THE BASE IMMEDIATELY SURROUNDING LUNKEN IS 3500 FT. (THE CLASS D LUNKEN AIRSPACE HAS 4 DIFFERENT BASE LEVELS OF CLASS B AIRSPACE IN IT OR ABOVE IT). MY PLANE WAS NOT OUTFITTED WITH GPS, BUT I DID HAVE DME. UNFORTUNATELY, SINCE THE CVG VOR IS NOT ON THE FIELD, MY DME WAS USELESS IN THIS EVENT. I RECOMMEND MOVING THE VOR TO THE CVG FIELD TO BETTER AID PLTS IN LOCATING THE BOUNDARIES OF THE CLASS B AIRSPACE. THE SECOND ISSUE CONCERNS THE SUGGESTED VFR FLYWAYS ON THE VFR TERMINAL AREA CHART FOR CINCINNATI. THE NE FLYING LINES UP PERFECTLY WITH THE PARALLEL RWYS OF LUNKEN FIELD. THAT MEANS TFC IN AND OUT OF THE CINCINNATI AREA AND LUNKEN TFC IS USING THE SAME AIRSPACE. THANKS TO THE LUNKEN TWR FOR KEEPING WATCH. THEY RPTED TFC TO ME AT 12 O'CLOCK POS, AND I HAD TO TAKE EVASIVE ACTION TO AVOID THE INCOMING ACFT. THIS INCIDENT OCCURRED ON THE OUTER RIM OF THE CLASS D AIRSPACE AT APPROX 2700 FT. MY SUGGESTION WOULD BE TO MOVE THE NE FLYWAY SO THE LUNKEN TFC ISN'T ON THE SAME COURSE. UNTIL THESE ISSUES GET CORRECTED, I'M GOING TO AVOID LUNKEN FIELD.
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.