Home Lawyers Litigation Contact Us Verdicts Search

Personal Injury

Planes/Helicopters

Research Center

Learn More

New York Aviation Accident Reports

Airports F - J

Ithaca Tompkins Regional

#561357

in this section: #535563 | #538594 | #561357

Aviation Accident Information for New York State: Ithaca Tompkins Regional Airport - Report #561357

The following report relates to an aviation accident that occurred at Ithaca Tompkins Regional Airport in September 2002 during dusk hours. The aircraft make/model involved in this Business flight was a Cessna 152 with 1 crew members. The observations in this report may have been made by a pilot, co-pilot, stewardess, flight attendant, or other aviation expert.

Common injuries sustained in airplane and helicopter accidents include bumps and bruises from service carts in the aisle, decompression injuries, broken bones, head and neck injuries from sudden descents, ascents and turbulence, and burns from hot food and beverages.

If you have been injured in a New York State aviation accident in an airplane, private jet, helicopter, either on the runway, takeoff, landing, or in flight, you may be able to get legal help and file a lawsuit to collect compensation for your pain and suffering with the help of an aviation accident attorney. To get started, please fill out this simple form. To assist a friend or loved one in need of legal advice, click here to tell them about Weitz & Luxenberg. Get help from an aviation accident lawyer today.

Report #: 561357
Data source: AVIATION SAFETY REPORTING SYSTEM
Aircraft Make/Model: Cessna 152
Flight Conduct Rule (if any): Part 91

Narrative:

as I approached the tompkins county airport, ithaca, ny (ith) on an ifr flt plan, in good vmc, I was given a hdof from elmira approach ctl to ith tower. I chked in with the tower and reported my location as 10 mI nne of the field and was instructed to rpt a r base for landing runway 32. another c172 was also approaching the field, but from the nw. I overheard a transmission from this aircraft stating his location as 5 mI nw (at this time, I was 7 mI nne of the airport). a few moments later, ith tower queried my pos, which I reported as being 5 mI n of the field. approx 1 min later, I called my r base entry for runway 32 (as instructed). approx 10 seconds later, I was informed of another cessna on r base and, after a pause of about 3 seconds, told to execute a l 360 deg turn. 90 degs into this turn, I was told to extend outbound for a straight-in approach runway 32. I complied and a normal landing was made. after I landed, ground ctl gave me a few words regarding the importance of pos rpts and chided me for rpting my pos as ne when I was nw and s of the field. I requested a phone number to discuss the matter further, and was told to use the fbo's intercom. I talked the matter over with one of the personnel in the tower who was unable to shed any light on the sit. he kept insisting that I was nw and then s of the field. I know that I was at no time w in the slightest deg of the field because my ifr routing put me on a direct tract from the massena vor (mss) to the ith vor, which results in a hdg of approx 210 des, a hdg that I flew with minor adjustments right into the r base entry from runway 32. what I took away from my conversation with the ctlr in the ith tower was a deep sense that the ctlr in question had lost situational awareness, due primarily to the lack of any form of radar surveillance (all they have is binoculars and a window). these ctlrs need a radar display, even if it is just a repeater off of another radar site. ith is an airport with fairly high tfc volume where commercial acr aircraft regularly mix with light ga planes. in the future, I will try to give more accurate pos rpts. I should have consistently reported my pos as being nne and not made the simple n xmission (although, I was mostly n of the field).

Synopsis:

twr lcl ctlr resolves potential airborne conflict by instructing the plt to circle and extend downwind behind another acft. the rptr was not coming from the pos the ctlr believed him to be.

Local Date:	September 2002
Local Quarter Time:	1201 To 1800
Facilty ID Nr Aircraft:	ITH.Airport
State of Facility Nr Acft:	NY
Magnetic Bearing (deg):	39
Facility Distance (nm):
Altitude AGL - LO(ft)
Altitude AGL - HI(ft)
Altitude MSL - LO(ft)
Altitude MSL - HI(ft)

Weather Conditions:
Ceiling:
Light Condition:	dusk
Runway Vis - LO(ft):
Runway Vis - HI(ft):
Visual Range - LO (sm):
Visual Range - HI (sm):

Operation Type

Carrier Operation:
GA Operation: Corporate
Other Operation:

Phase of Flight

Climbout:
Climbout Other:
Cruise:
Other Cruise:
Descent: Intermediate Altitude
Other Descent:
Ground:
Other Ground:
Landing
Other Landing:
Other Flight Phase:

Airspace Info

Class A:
Class B:
Class C:
Class D: ITH.D
Class E:
Class G:
Special Use:
Temp Use:

Findings For Aircraft Sequence 2

General Info

	Acft Make/Model Desc:				Skyhawk 172/Cutlass 172
	Crew Count:				1
	Passenger Count:
	Aircraft Involved:
	Flight Conduct Rule:				Part 91
	Flight Purpose:

Operation Type

	Carrier Operation:
	GA Operation:				Personal
	Other Operation:

Phase of Flight

	Climbout:
	Climbout Other:
	Cruise:
	Other Cruise:
	Descent:				Intermediate Altitude
	Other Descent:
	Ground:
	Other Ground:
	Landing
	Other Landing:
	Other Flight Phase:

Airspace Info

	Class A:
	Class B:
	Class C:
	Class D:				ITH.D
	Class E:
	Class G:
	Special Use:
	Temp Use:

Findings

Anomaly Descriptors

	Acft Equip Anomaly:
	ASP Anomaly:
	Alt Dev Anomaly:
	Cabin Event Anomaly:
	Conflict Anomaly:
	Excursion Anomaly:
	Ground Encounter Anomaly:
	Incursion Anomaly:
	In-Flight Anomaly:
	Maintenance Anomaly:
	Non-Adherence Anomaly:
	Non-Adherence Other Anomaly:
	Other Anomaly:
	Other Spatial Dev. Anomaly:

Anomaly Consequences

	Consequence Desc:				Reviewed Incident With Flight Crew
	Other Consequence Desc:
	Misc. Consequence Desc:				ACCURATE POSITION RPTS

Anomaly Detected By

	Controller A:				3
	Controller B:
	Crew A:
	Crew B:

Anomaly Resolution

	Aircraft:
	Controller:				Separated Traffic
	Crew:
	Other Action:
	No Action:
	Event Type:				Unwanted Situation

Reporter Information

Findings For Reporter Sequence 1

Reporter Function

	Controller:
	Flight Attendant:
	Flight Crew:				Single Pilot
	Instructor:
	Maintenance:
	Observer:
	Other Personell:
	Oversight:				PIC
	Reporter Activity:				Pilot Flying

Findings For Reporter Sequence 2

Reporter Function

	Controller:
	Flight Attendant:
	Flight Crew:				Single Pilot
	Instructor:
	Maintenance:
	Observer:
	Other Personell:
	Oversight:				PIC
	Reporter Activity:				Pilot Flying

Findings For Reporter Sequence 3

Reporter Function

	Controller:				Local
	Flight Attendant:
	Flight Crew:
	Instructor:
	Maintenance:
	Observer:
	Other Personell:
	Oversight:
	Reporter Activity:				Controlling

END REPORT

Click To Talk To Us Online

This information has been provided by the Federal Aviation Administration (FAA)

#535563

New York State Aviation Accident Lawsuit: Ithaca Tompkins Regional Airport Report #535563
Ithaca Tompkins Regional Airport Aviation Accident Info: Bonanza 35 Aircraft

#538594

New York State Aviation Accident Lawsuit: Ithaca Tompkins Regional Airport Report #538594
Ithaca Tompkins Regional Airport Aviation Accident Info: PA-28 Cherokee/Archer Ii/Dakota/Pillan/Warrior Aircraft

2002

New York Aviation Accident Lawsuit Information: Ithaca Tompkins Regional Airport 2002
Ithaca Tompkins Regional 2002 Airport NY State Aviation Accident Lawsuit Attorney/Lawyer

Name

Phone

strictly confidential

Your Question

First Name:
Last Name:
Home Phone:
City & State:
Email:
Where were you injured?
Was the Aircraft Commercial or Private?
Describe your Aviation Injury:
Was your flight international or domestic?
Where did you hear about Weitz & Luxenberg?
Additional Comments: