Narrative:

On wed, june, 1990, I called clearance delivery with juliet. I was told 'on request' that night clearance delivery's xmissions were scratchy and it sounded like a hand held radio (weak). Clearance delivery came back with ...runway heading, cleared as filed, (at initial altitude, transmission became scratchy), I heard 3000' inspect 5000', departure req 119.7 and squawk XXXX I read back the clearance. Clearance delivery came back with 'readback correct.' on the climb out, I was switched over to departure. 'Reported out of one point three for three thousand.' no response from departure. (Departure was busy with other aircraft). At 2300' radar indent was given with traffic reports at 12 O'clock and 1 O'clock. After being radar vector toward salisbury, a frequency change was given 'contact baltimore approach on 124.55.' after making the initial call at 3000' with the controller on 124.55, he climbed us to 5000' and direct salisbury. He inquired where we received 3000'. I told him in the clearance. His strip read 2000' expect 5000'. He told us he would look into why we were given 3000'. I feel the contributing factors to the situation were; scratchy radio xmissions during clearance, failure to catch the mistake during readback and climb out. To my best knowledge, there was no conflicting traffic.

Related reports:

Google
 

Original NASA ASRS Text

Title: COMMUTER MDT ALT DEVIATION OVERSHOT DURING CLIMB OUT FROM BWI.

Narrative: ON WED, JUNE, 1990, I CALLED CLRNC DELIVERY WITH JULIET. I WAS TOLD 'ON REQUEST' THAT NIGHT CLRNC DELIVERY'S XMISSIONS WERE SCRATCHY AND IT SOUNDED LIKE A HAND HELD RADIO (WEAK). CLRNC DELIVERY CAME BACK WITH ...RWY HDG, CLRED AS FILED, (AT INITIAL ALT, XMISSION BECAME SCRATCHY), I HEARD 3000' INSPECT 5000', DEP REQ 119.7 AND SQUAWK XXXX I READ BACK THE CLRNC. CLRNC DELIVERY CAME BACK WITH 'READBACK CORRECT.' ON THE CLBOUT, I WAS SWITCHED OVER TO DEP. 'RPTED OUT OF ONE POINT THREE FOR THREE THOUSAND.' NO RESPONSE FROM DEP. (DEP WAS BUSY WITH OTHER ACFT). AT 2300' RADAR INDENT WAS GIVEN WITH TFC RPTS AT 12 O'CLOCK AND 1 O'CLOCK. AFTER BEING RADAR VECTOR TOWARD SALISBURY, A FREQ CHANGE WAS GIVEN 'CONTACT BALTIMORE APCH ON 124.55.' AFTER MAKING THE INITIAL CALL AT 3000' WITH THE CTLR ON 124.55, HE CLBED US TO 5000' AND DIRECT SALISBURY. HE INQUIRED WHERE WE RECEIVED 3000'. I TOLD HIM IN THE CLRNC. HIS STRIP READ 2000' EXPECT 5000'. HE TOLD US HE WOULD LOOK INTO WHY WE WERE GIVEN 3000'. I FEEL THE CONTRIBUTING FACTORS TO THE SITUATION WERE; SCRATCHY RADIO XMISSIONS DURING CLRNC, FAILURE TO CATCH THE MISTAKE DURING READBACK AND CLBOUT. TO MY BEST KNOWLEDGE, THERE WAS NO CONFLICTING TFC.

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.