<< >> NASA ASRS Report 148564, June 1990

Small aircraft pilot making practice ILS approach descends into air traffic area of airport along approach route.

Attributes
ACN	148564
Time
Date	199006
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : ttn
State Reference	NJ
Altitude	msl bound lower : 2700 msl bound upper : 4500
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : phl tower : ttn
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach
Flight Plan	None
Person 1
Affiliation	Other
Function	other personnel other
Qualification	pilot : commercial pilot : instrument
Experience	flight time last 90 days : 30 flight time total : 300 flight time type : 65
ASRS Report	148564
Person 2
Affiliation	Other
Function	flight crew : single pilot
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : insufficient time other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were returning to northeast pne VFR at night, when we were 20 or so mi from our destination, we began our descent from 4500' as we tuned in the ILS-24 at pne and made a small turn to intercept the localizer. We were receiving traffic advisories from TRACON and as we descended through 2700' MSL (approximately 2600' AGL) the controller asked if we were cleared into trenton's air traffic area. We responded negative and then looked around and realized where we were. We had been so engrossed in setting up for the approach that we were oblivious to trenton's proximity. At the time of the infraction, the plane was being flown by a friend in the right seat (he is a CFI). We fly together often and share plting 50/50. Whoever is not flying handles all radio and navigation work. Since I was navigating, I feel I am at least 50% responsible for allowing this to happen. But legally, the PIC is probably responsible. The question is, who was the PIC at the time? My friend and I do not have a standing rule on this. We probably should in the future.

Related reports:

• Close proximity GA small aircraft in sfb air traffic area ma...
• Aircraft in traffic pattern making touch and goes fails to c...
• The pilot of a small homebuilt high performance aircraft rep...
• Close proximity GA small aircraft on straight in approach an...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: SMA PLT MAKING PRACTICE ILS APCH DESCENDS INTO ATA OF ARPT ALONG APCH ROUTE.

Narrative: WE WERE RETURNING TO NE PNE VFR AT NIGHT, WHEN WE WERE 20 OR SO MI FROM OUR DEST, WE BEGAN OUR DSNT FROM 4500' AS WE TUNED IN THE ILS-24 AT PNE AND MADE A SMALL TURN TO INTERCEPT THE LOC. WE WERE RECEIVING TFC ADVISORIES FROM TRACON AND AS WE DSNDED THROUGH 2700' MSL (APPROX 2600' AGL) THE CTLR ASKED IF WE WERE CLRED INTO TRENTON'S ATA. WE RESPONDED NEGATIVE AND THEN LOOKED AROUND AND REALIZED WHERE WE WERE. WE HAD BEEN SO ENGROSSED IN SETTING UP FOR THE APCH THAT WE WERE OBLIVIOUS TO TRENTON'S PROX. AT THE TIME OF THE INFRACTION, THE PLANE WAS BEING FLOWN BY A FRIEND IN THE R SEAT (HE IS A CFI). WE FLY TOGETHER OFTEN AND SHARE PLTING 50/50. WHOEVER IS NOT FLYING HANDLES ALL RADIO AND NAV WORK. SINCE I WAS NAVIGATING, I FEEL I AM AT LEAST 50% RESPONSIBLE FOR ALLOWING THIS TO HAPPEN. BUT LEGALLY, THE PIC IS PROBABLY RESPONSIBLE. THE QUESTION IS, WHO WAS THE PIC AT THE TIME? MY FRIEND AND I DO NOT HAVE A STANDING RULE ON THIS. WE PROBABLY SHOULD IN THE FUTURE.

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.