37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 628654 |
Time | |
Date | 200408 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : f45.airport |
State Reference | FL |
Altitude | msl single value : 2000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pbi.tracon |
Operator | general aviation : personal |
Make Model Name | PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Route In Use | enroute : on vectors |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | instruction : instructor |
Qualification | pilot : commercial pilot : multi engine pilot : instrument pilot : cfi |
ASRS Report | 628654 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | airspace violation : entry non adherence : far |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Airspace Structure Flight Crew Human Performance |
Primary Problem | Airspace Structure |
Narrative:
While on a VFR training flight we were practicing instrument approachs to an uncontrolled airport. We had requested VFR approachs through the controling ATC agency, had received a squawk code, and were receiving radar vectors for the approach. While on vectors we penetrated an adjacent class D airspace for a private airport. I was not sure whether or not this airspace was active at the time since the sectional chart states this airspace is class D or east by NOTAMS, and I did not see any NOTAMS for this area before takeoff. Because this was a VFR flight I was unsure if we needed to remain clear of the airspace since we had received a squawk code and we were receiving radar vectors for an approach from the approach controller. I did not realize the problem until we were in the class D airspace. I became complacent due to the fact that we did have a squawk code and we were receiving vectors. One way to avoid the problem would be to have better situational awareness with regard to the VFR sectional. Another way to avoid the problem would be to ask the controller, we were receiving vectors from, if we needed to take any corrective actions to avoid the airspace.
Original NASA ASRS Text
Title: PA28 PLT IS CONCERNED ABOUT ENTERING CLASS D AIRSPACE DURING RADAR VECTORS FROM PBI TRACON.
Narrative: WHILE ON A VFR TRAINING FLT WE WERE PRACTICING INST APCHS TO AN UNCTLED ARPT. WE HAD REQUESTED VFR APCHS THROUGH THE CTLING ATC AGENCY, HAD RECEIVED A SQUAWK CODE, AND WERE RECEIVING RADAR VECTORS FOR THE APCH. WHILE ON VECTORS WE PENETRATED AN ADJACENT CLASS D AIRSPACE FOR A PVT ARPT. I WAS NOT SURE WHETHER OR NOT THIS AIRSPACE WAS ACTIVE AT THE TIME SINCE THE SECTIONAL CHART STATES THIS AIRSPACE IS CLASS D OR E BY NOTAMS, AND I DID NOT SEE ANY NOTAMS FOR THIS AREA BEFORE TKOF. BECAUSE THIS WAS A VFR FLT I WAS UNSURE IF WE NEEDED TO REMAIN CLR OF THE AIRSPACE SINCE WE HAD RECEIVED A SQUAWK CODE AND WE WERE RECEIVING RADAR VECTORS FOR AN APCH FROM THE APCH CTLR. I DID NOT REALIZE THE PROB UNTIL WE WERE IN THE CLASS D AIRSPACE. I BECAME COMPLACENT DUE TO THE FACT THAT WE DID HAVE A SQUAWK CODE AND WE WERE RECEIVING VECTORS. ONE WAY TO AVOID THE PROB WOULD BE TO HAVE BETTER SITUATIONAL AWARENESS WITH REGARD TO THE VFR SECTIONAL. ANOTHER WAY TO AVOID THE PROB WOULD BE TO ASK THE CTLR, WE WERE RECEIVING VECTORS FROM, IF WE NEEDED TO TAKE ANY CORRECTIVE ACTIONS TO AVOID THE 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.