 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Mooney M20 pilot reported being advised by bos ATC to contact them before operating in close proximity to the overlying class C airspace.
| Attributes | |
| ACN | 1366973 |
| Time | |
| Date | 201606 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | CON.Airport |
| State Reference | NH |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | M-20 J (201) / Allegro |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | None |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Private |
| Experience | Flight Crew Last 90 Days 45 Flight Crew Total 1294 Flight Crew Type 700 |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
I was practicing multiple approaches to the con airport in night VFR conditions. My second approach was the ILS 35 which I elected to fly at 2;400 ft to remain under the overlying 2;500 ft class C airspace at mht to the south. After completing the procedure turn I was descending inbound on the glideslope when another aircraft called me on unicom and said bos center would like me to contact them.I called bos and was asked if I was aware of the mht class C airspace. I responded that I was and explained I purposely flew the approach at 2;400 ft to remain under the class C. I was told by the controller the class C is at 2;000 ft and in the future I must contact them before attempting the ILS to 35 at con.as I continued to fly the missed approach I was approx 1 mile north of the con airport when the bos controller called me again and said that 'after checking the chart' the airspace in question was indeed 2;500 ft but it would be good policy to contact them prior to flying close to the class C.at no time during the ILS 35 approach did my aircraft climb above 2;400 ft. There was very little wind and I flew the approach as published which clearly kept me out of the mht class C airspace; however to avoid any potential confusion in the future I will contact bos center when operating near the class C.
Original NASA ASRS Text
Title: Mooney M20 pilot reported being advised by BOS ATC to contact them before operating in close proximity to the overlying Class C airspace.
Narrative: I was practicing multiple approaches to the CON airport in night VFR conditions. My second approach was the ILS 35 which I elected to fly at 2;400 ft to remain under the overlying 2;500 ft Class C airspace at MHT to the south. After completing the procedure turn I was descending inbound on the glideslope when another aircraft called me on unicom and said BOS Center would like me to contact them.I called BOS and was asked if I was aware of the MHT class C airspace. I responded that I was and explained I purposely flew the approach at 2;400 ft to remain under the class C. I was told by the Controller the Class C is at 2;000 ft and in the future I must contact them before attempting the ILS to 35 at CON.As I continued to fly the missed approach I was approx 1 mile north of the CON airport when the BOS controller called me again and said that 'after checking the chart' the airspace in question was indeed 2;500 ft but it would be good policy to contact them prior to flying close to the Class C.At no time during the ILS 35 approach did my aircraft climb above 2;400 ft. There was very little wind and I flew the approach as published which clearly kept me out of the MHT Class C airspace; however to avoid any potential confusion in the future I will contact BOS center when operating near the Class C.
Data retrieved from NASA's ASRS site 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.