Descended too soon flying lost communication procedure.

Attributes
ACN	102271
Time
Date	198901
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : ewc
State Reference	PA
Altitude	msl bound lower : 3000 msl bound upper : 7000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zob
Operator	general aviation : personal
Make Model Name	Small Aircraft
Flight Phase	cruise other descent : approach descent other
Route In Use	enroute other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : commercial
Experience	flight time last 90 days : 25 flight time total : 1000 flight time type : 500
ASRS Report	102271
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	aircraft equipment problem : less severe altitude deviation : excursion from assigned altitude non adherence : far
Independent Detector	other flight crewa other other : unspecified
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was on an IFR flight plan between cross keys, nj, and the beaver county airport in beaver falls, PA. I lost communications at 7000' MSL between the johnstown and ellwood city VOR's. I spent several mins trying to restore communications, but I was unsuccessful. I then reset my transponder code to 7700 for 1 min, and then set it to 7600. I planned a VOR 28 approach into beaver county, which calls for departing the ellwood city VOR at 3000' MSL. I began a descent in VFR conditions 20 mi east of the ellwood city VOR to allow me to cross the VOR at 3000' MSL and shoot the approach. I began my descent east of the VOR because I was a little behind my ETA and wanted to expedite the remainder of my flight. But, the lost communication procedure calls for the pilot to maintain assigned altitude until crossing the initial approach fix. I successfully shot the approach and landed at beaver county. I believe this failure to follow published procedure could have been avoided by maintaining familiarity with IFR lost communications procedures.

Original NASA ASRS Text

Title: DESCENDED TOO SOON FLYING LOST COM PROC.

Narrative: I WAS ON AN IFR FLT PLAN BTWN CROSS KEYS, NJ, AND THE BEAVER COUNTY ARPT IN BEAVER FALLS, PA. I LOST COMS AT 7000' MSL BTWN THE JOHNSTOWN AND ELLWOOD CITY VOR'S. I SPENT SEVERAL MINS TRYING TO RESTORE COMS, BUT I WAS UNSUCCESSFUL. I THEN RESET MY XPONDER CODE TO 7700 FOR 1 MIN, AND THEN SET IT TO 7600. I PLANNED A VOR 28 APCH INTO BEAVER COUNTY, WHICH CALLS FOR DEPARTING THE ELLWOOD CITY VOR AT 3000' MSL. I BEGAN A DSCNT IN VFR CONDITIONS 20 MI E OF THE ELLWOOD CITY VOR TO ALLOW ME TO CROSS THE VOR AT 3000' MSL AND SHOOT THE APCH. I BEGAN MY DSCNT E OF THE VOR BECAUSE I WAS A LITTLE BEHIND MY ETA AND WANTED TO EXPEDITE THE REMAINDER OF MY FLT. BUT, THE LOST COM PROC CALLS FOR THE PLT TO MAINTAIN ASSIGNED ALT UNTIL XING THE INITIAL APCH FIX. I SUCCESSFULLY SHOT THE APCH AND LANDED AT BEAVER COUNTY. I BELIEVE THIS FAILURE TO FOLLOW PUBLISHED PROC COULD HAVE BEEN AVOIDED BY MAINTAINING FAMILIARITY WITH IFR LOST COMS PROCS.

Data retrieved from NASA's ASRS site as of August 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.