Possible incursion of class 'B' airspace.

Attributes
ACN	300158
Time
Date	199503
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : yip
State Reference	MI
Altitude	msl bound lower : 2700 msl bound upper : 2700
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : yip tower : bwi
Operator	general aviation : personal
Make Model Name	Mustang (P51)
Operating Under FAR Part	Part 91
Flight Phase	other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 75 flight time total : 6850 flight time type : 0
ASRS Report	300158
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	aircraft equipment problem : less severe altitude deviation : overshoot non adherence : far other anomaly other
Independent Detector	other controllera
Resolutory Action	flight crew : became reoriented other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

1) first flight in P-51 mustang at yip. Controllers had many aircraft in closed traffic. 2) after takeoff, I requested local traffic be approved or pilot options at 2500 ft MSL. Wanted to stay close to the airport due to it being the first flight. 3) tower was complaining of bad radio xmissions. I was issued traffic in the pattern and was looking for that traffic. At about base leg, the tower issued an alert to remain clear of the class B airspace at detroit metropolitan airport. 4) I replied that we were at 2700 ft and were clear. The tower issued an altitude setting and that setting was confirmed on our altitude. 5) during our climb, while looking for traffic, I can't indicate what altitude the aircraft was operating at, but feel it was not in the class B airspace. 6) more and active awareness of altitude and airspeed needs to be monitored by the pilot and the control tower when operating high performance fighter aircraft in traffic pattern or class D airspace. 7) no further alerts or notifications were given. No requirement to call the tower or approach control. 8) may be advisable to be sure tower controller clearly understands our request to remain in class D airspace, 1000 ft above pattern altitude.

Original NASA ASRS Text

Title: POSSIBLE INCURSION OF CLASS 'B' AIRSPACE.

Narrative: 1) FIRST FLT IN P-51 MUSTANG AT YIP. CTLRS HAD MANY ACFT IN CLOSED TFC. 2) AFTER TKOF, I REQUESTED LCL TFC BE APPROVED OR PLT OPTIONS AT 2500 FT MSL. WANTED TO STAY CLOSE TO THE ARPT DUE TO IT BEING THE FIRST FLT. 3) TWR WAS COMPLAINING OF BAD RADIO XMISSIONS. I WAS ISSUED TFC IN THE PATTERN AND WAS LOOKING FOR THAT TFC. AT ABOUT BASE LEG, THE TWR ISSUED AN ALERT TO REMAIN CLR OF THE CLASS B AIRSPACE AT DETROIT METROPOLITAN ARPT. 4) I REPLIED THAT WE WERE AT 2700 FT AND WERE CLR. THE TWR ISSUED AN ALT SETTING AND THAT SETTING WAS CONFIRMED ON OUR ALT. 5) DURING OUR CLB, WHILE LOOKING FOR TFC, I CAN'T INDICATE WHAT ALT THE ACFT WAS OPERATING AT, BUT FEEL IT WAS NOT IN THE CLASS B AIRSPACE. 6) MORE AND ACTIVE AWARENESS OF ALT AND AIRSPD NEEDS TO BE MONITORED BY THE PLT AND THE CTL TWR WHEN OPERATING HIGH PERFORMANCE FIGHTER ACFT IN TFC PATTERN OR CLASS D AIRSPACE. 7) NO FURTHER ALERTS OR NOTIFICATIONS WERE GIVEN. NO REQUIREMENT TO CALL THE TWR OR APCH CTL. 8) MAY BE ADVISABLE TO BE SURE TWR CTLR CLRLY UNDERSTANDS OUR REQUEST TO REMAIN IN CLASS D AIRSPACE, 1000 FT ABOVE PATTERN ALT.

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.