Hamilton v. United States

343 F. Supp. 426
CourtDistrict Court, N.D. California
DecidedOctober 22, 1971
DocketC-48398, C-48454, C-48618 and C-50802
StatusPublished
Cited by6 cases

This text of 343 F. Supp. 426 (Hamilton v. United States) is published on Counsel Stack Legal Research, covering District Court, N.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Hamilton v. United States, 343 F. Supp. 426 (N.D. Cal. 1971).

Opinion

MEMORANDUM OF DECISION

CONTI, District Judge.

These actions arise out of the mid-air collision of two small twin-engined planes, a Piper Apache and a Cessna 310, at a point about one-half mile from the threshold of Runway 27 at Oakland Airport on Friday, February 17, 1967. At the time of the accident, about 2.30 p. m., Visual Flight Rules (VFR) were in effect. Mr. Hamilton and Mr. Whitlow, the two pilots in the Cessna 310, 1 were killed, and Mr. Van Gilder, the pilot of the Piper Apache, 2 was injured. The three plaintiffs subsquently brought *428 these actions against the United States under the Federal Tort Claims Act, 28 U.S.C. §§ 1346, 2671-2680, claiming, in essence, that the accident was caused by the negligence of the air traffic controllers, agents of the United States. Also consolidated in this trial is an action for property damage brought pursuant to the provisions of the Federal Tort Claims Act; the plaintiffs, Lewis & Clark Trading Co., and H. J. Stockman, doing business as Lewis & Clark Trading Co., are the purported owners of the Cessna, N3608D, being flown by Hamilton and Whitlow.

At the time of the accident, flight visibility was about four miles with haze and smoke, and air traffic at the Oakland Airport was moderate to heavy. Visual Flight Rules (VFR) were in effect. Under VFR conditions (commonly referred to as “see and be seen” conditions), unlike Instrument Flight Rule (IFR) conditions, pilots navigate aircraft and execute takeoffs and landings visually and not by instruments.

At Oakland Airport runways 27 right (27R) and 27 left (27L) are parallel runways running in a direction from east to west. The runways are each 150 ft. in width and are separated by 1000 ft. from the center line o.f runway 27R to center-line of runway 27L. At the time in question, all the aircraft using runways 27R and 27L were landing at the east threshold of the runways and taking off towards the west. There was testimony by tower controller McCready that two planes could land simultaneously on runways 27R and 27L; this was done and was permissible.

The air traffic control tower is situated to about a mile south of runways 27 and near their eastern end, it is approximately 5600 ft. from tower to landing threshold of 27R, and 4500 ft. to landing threshold of 27L. The air traffic control function on runways 27 was being performed by Mr. Story, an experienced air traffic controller who had transferred to Oakland only recently. 3 Mr. Story’s activities were being monitored by Mr. McCready, an experienced controller who was more familiar with Oakland airport.

Under the radio system in use at Oakland, the Cessna and the Apache could hear the transmissions from the tower to them and to other aircraft operating in the control zone on the same frequency. Likewise, both aircraft could hear all transmissions from other aircraft to the tower. On the day in question, because of haze and smoke in the area toward the east, and because of the outlying hills, the ability of the controllers to see traffic approaching from the east was decreased.

There was a radar scope in the tower; however, no evidence was produced as to the “practice” to utilize this scope, it being referred to as a “Mickey Mouse” scope, and evidence was presented in that it was not customary to use this equipment as it had certain limitations.

At 218.45 p. m. the Cessna 310 reported to the tower that it was over Castro Valley, an area about 8 miles east of the airport, and indicated an intention to land. Two seconds later, Mr. Story authorized the 310 to make a straight in approach to runway 27R and instructed it to report on two mile final, i. e., two miles from the end of the runway. The 310 promptly acknowledged receipt of this instruction. At this point the 310 may have been travelling at an approach speed of about 120 m. p. h. (or two miles per minute). Mr. Story then turned his attention to other planes in the airport traffic area. 4

During the next four and one-half minutes the control tower exchanged radio communications at least once with *429 eleven different planes (apart from the Cessna 310), and exchanged several communications with many of these eleven planes. At 223.18, 4 minutes and 33 seconds after the 310 contacted the tower, and the 310 not having reported at two-mile final as it was instructed to, Mr. Story called the 310 and expressly requested its position. No answer was received..

At 223.25, seven seconds later, Mr. Story called the 310 a second time. Again, no answer was received.

From 223.25, when Mr. Story called the 310 a second time, until 223.46, twenty-one seconds later, neither the 310 nor any other plane contacted the tower. At the later time, and the 310 still not having answered, Mr. Story called the 310 for the third time. For the third time no response was transmitted to the control tower. At this time neither Mr. Story (nor Mr. McCready, who was monitoring his activities) could sight the 310.

Shortly thereafter, at 223.48, the Piper Apache contacted the tower, reporting its position as 5 DME miles from the airport on the two seven right localizer. 5 At 224.20 Mr. Story authorized the Apache to continue a straight in approach for runway 27R, and expressly instructed it to report “crossing the freeway on two mile final.” 6 Mr. Story then communicated with another plane (nine zero fox) (90F).

At 225.06, well more than six minutes after it reported at Castro Valley, the Cessna 310 reported to the tower that it was “coming up on the freeway” for runway 27R. 7 Mr. Story then authorized the 310 to “continue straight in approach”. At this time Mr. Story did not have the 310 in sight and he did not give it a clearance to land.

Mr. Van Gilder heard the 310 reporting in as any pilot could who was tuned to the same frequency. Although under VFR conditions the pilot has the primary duty to “see and be seen”, and can, therefore, be expected to listen carefully for any traffic in his vicinity, nevertheless, at 225.17, Mr. Story expressly informed the Apache that a Cessna had reported approaching the freeway on two mile final. 8 The tower did not have either in sight at this time.

. During the approximately one-half minute after informing the Apache of the 310’s position, Mr. Story communicated with two other aircraft in the control zone. One plane, zero seven kilo (07K), reported over Lake Chabot (a point about 6 miles east north east of runway 27R), and was instructed to enter the right traffic pattern. 9 The other plane, four nine juliette (49J), was travelling due east on a line parallel to and south of 27L; Mr. Story cleared 49J for a touch and go landing on 27L. 10

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Management Activities, Inc. v. United States
21 F. Supp. 2d 1157 (C.D. California, 1998)
Thurston v. United States
888 F. Supp. 1100 (D. Utah, 1995)
Worthington v. United States
807 F. Supp. 1545 (N.D. Georgia, 1992)
Crossman v. United States
378 F. Supp. 1312 (D. Oregon, 1974)
Allen v. United States
370 F. Supp. 992 (E.D. Missouri, 1973)

Cite This Page — Counsel Stack

Bluebook (online)
343 F. Supp. 426, Counsel Stack Legal Research, https://law.counselstack.com/opinion/hamilton-v-united-states-cand-1971.