Ground collision pictures

[blue up]

Sorry.

This is the LEAST incorrect forum, I think

I'm after a sobering picture to add to a rather uninspiring refresher course module on runway incursions. No luck finding anything suitable on the web. Any suggested pics to remind bods just how nasty a runway collision is?

I tried the 330 at Paris and the obvious TFN but neither gave me suitable pics

Over to yoos guys.

[evansb]

Doug Scroggins has posted some photos on airliners.net of the 1996 Quincy, IL ground collision between a Beech 1900 and a King Air.

[Tiger_mate]

Google 'Tenerife crash'
http://www.pbs.org/wgbh/nova/planecrash/images/minu-tenerifecrash7-l.jpg

[Flying Lawyer]

Not a runway incursion,
but a sobering reminder of the importance of weaving the nose in a taildragger.



http://img.photobucket.com/albums/v146/FlyingLawyer/scraprv1_900.jpg



http://img.photobucket.com/albums/v146/FlyingLawyer/scraprv2_900.jpg


FL

[blue up]

That's more the sort of thing I was after. TFN has been used too often and I think people have learnt the lessons of that one without concidering other possible cock-ups.

This time I'm targetting runway markings, language and callsign confusion.

[forget]

Look for SQ 006. There are some awful shots of this one.

http://news.bbc.co.uk/1/hi/world/asia-pacific/1001152.stm

[WHBM]

SQ 006 was not a runway incursion. It was attempting taking off on a closed runway and collided with construction equipment legitimately there.

[forget]

SQ 006 was not a runway incursion. It was attempting taking off on a closed runway and collided with construction equipment legitimately there.

Oh yes it was.

ICAO DEFINITION. RUNWAY INCURSION.
Any occurrence at an aerodrome involving the incorrect presence of an aircraft, vehicle or person on the protected area of a surface designated for the landing and take off of aircraft.

PS. The ICAO definition of a runway incursion is adopted in the UK with effect from 1 January 2007. CAP 168 Chapter 2 Appendix 2D will be amended at the next opportunity.

[forget]

Blue Up; You asked for Call-Sign Confusion Incidents. Here's the US's WORST EVER AIRPROX - which, and I followed it at the time, barely made the press. And you try and find the report now.

( WHBM. This is also a Runway Incursion.);)

Summarised from ASRS Report Number 269000. Near Mid Air Collision.
Date/Local Time. 94/04. 18:01. Facility Cincinnati/Northern Kentucky Intl. OH
Weather Conditions: VMC. Daylight. Visual Range 5.00 Miles.
Flight Phase. Take Off.
Aircraft. B737, MD-88.

Anomaly resolution: Avoidance, evasive action.

Primary problem area: Air Traffic Control ( Human Factors)

Horizontal Separation 300 Feet. Vertical Separation NIL.

Narrative, Controller.

Aircraft X was told to taxi into position and hold on runway 27 for traffic departing on runway 18R. Aircraft Y was told to taxi into position and hold on runway 18R because of a previous departure on runway 18R. When the previous runway 18R departure
was no longer a factor I told Y ‘At the MM turn right Hdg 210 Degs, runway 18R cleared for takeoff’. I scanned the runway, looked at the previous departure to make sure the aircraft turned out on the noise track. I looked up at the Brite radar, looked back
down to observe the runway 18R departure Y and re-scan the runway. I then wrote down my next 18R departure and looked back up to see Y and X departing simultaneously from intersecting runways. At this time there was nothing I could do to avoid the simultaneous departure. I used proper phraseology for crossing runways and I believe I heard only the read-back of Y off runway 18R. X was never issued a departure clearance nor did I hear X read back a clearance.

Narrative. Flight Crew X.

1. Aircraft X cleared by tower to ‘taxi into position and hold runway 27.’ I (PNF) acknowledged ‘X position and hold runway 27.’ As we completed the final items of the takeoff checklist, the tower transmitted ‘X turn left Hdg 210, cleared for takeoff.’ I responded ‘Hdg 210, X cleared for takeoff runway 27.’ As we lifted off and passed the intersection of runways 18R/27, I observed a company MD88 approaching the same intersection on runway 18R. The first half runway 18R was not visible from our position. The initial 210 Hdg was unusual for a takeoff on runway 27.

2. Aircraft X cleared to taxi into position and hold runway 27. The First Officer read back ‘aircraft X position and hold runway 27’. About 30 seconds later we received takeoff clearance ‘aircraft X fly Hdg 210, cleared for takeoff.’ We acknowledged and commenced our takeoff roll. At rotation we observed another jet approaching the intersection of our 2 runways (27 and 18R). We passed ahead of and above oncoming aircraft and continued a normal takeoff. Factors that contributed to the problem; We had somewhat similar call signs. We were not aware of another company jet departing 18R. The first portion of runway 18R is not visible from runway 27. If the controller had shared the information that he had 2 aircraft in position for takeoff I don’t think this would have occurred.

Narrative, Pilot Y.

Aircraft Y was cleared into position and hold runway 18R. We read back ‘cleared into position and hold runway 18R aircraft Y’. After approximately 4 seconds CVG tower transmitted ‘aircraft Y fly Hdg 210 cleared for takeoff runway 18R.’ my First Officer rogered ‘Hdg 210 cleared for takeoff runway l8R aircraft Y.’ At 145 kts during rotation, as our main wheels left the ground approximately 600 ft short of runway 18R/27 intersection, we noticed a company 737 rotating on runway 27 prior to the runway intersection. We deviated left behind his rotation. He passed approximately 300 ft just to the right of our nose. Company flight was aircraft X which is a similar sounding call sign. At no time did we hear tower and X communicate about position and hold or cleared for take-off. It is our assumption that aircraft X read back our clearance at the same time as us, mistaking our call sign.

Report Synopsis:

Multiple runway operation, intersecting runways, similar call signs.
Aircraft X unauthorized takeoff. Near Mid Air Collision with aircraft Y.

[Brian Abraham]

Don't know if this is of help. F4U collision with stationary F8F on take off at Oshkosh. Better quality video than this available on the web some where.
http://www.youtube.com/watch?v=uvd0laIhO38

[Swanie]

A question for the flying lawyer;

How do you get skid marks on a taxiway??:eek:

[con-pilot]

How do you get skid markes on a taxiway

Take another look, those are not skid marks from a landing aircraft. Those are marks left by overheated main gear tires after landing. Very common on concrete taxiways.

[Swanie]

overheated tyres can leave rubber on taxiway's?? Interesting.. well I've learnt my one new thing today :ok:
But why in photo 1, the left hand one seems to "fade away":confused:

[evansb]

As a prelude to the Tenerife disaster, on January 29, 1971, at Sydney Kingsford International Airport, a departing TAA Boeing 727, just airborne, severed the tail of a CP Air Douglas DC-8-63, just exiting the runway. The TAA 727 landed safely. More people have forgotten about this incident than remember it. Perhaps the epilogue would be the near-collision between a WJA 737 and a NWA Airbus at LAX yesterday. http://i141.photobucket.com/albums/r68/convair640/cpair-tail-wheatley.jpg

[helen-damnation]

Can't remember much of the details but there was an incident in LHR about 7 years ago which involved an aircraft lining up with another on finals and a very close go-around.
I think one of the a/c was from British Midland/BMI.
One of the recommendations that came from the incident report was turning the strobes on when on an active runway.
Regards,
H-D

['Chuffer' Dandridge]

The tyre marks seem to be too wide and too narrow a wheelbase for an aircraft. Maybe a bored ATCO doing the runway inspection and testing the brakes....:E

[PAXboy]

I see that Airliners dot net do not have any images categorised under 'runway incursion'. Using the word 'collision' in the search reveals that many of the photographers who feed the site are obsessed with catching the collision avoidance beacon flash at the moment that they take the picture. :zzz: They also show images of a/c that had a collision a few days/weeks later. :confused:

However, they do have some images that show the results of taxy encounters and these might serve to show the results, even if the actual circumstances are not detailed as you would like.

I hope these links will take you to the images with the following caption from 2004:
N87GL (cn UC-87) United Express / Great Lakes Flight 5925/5926 took off from Chicago. As the Beechcraft was approaching Quincy, two aircraft were ready for departure. Beechcraft King Air 65-A90 (N1127D) and Piper Cherokee N7646J were taxiing to runway 04. United Express crew continued their approach to runway 13. The King Air however, had taxied onto the runway and had started it's take-off roll when the Beech 1900 touched down. A collision took place at the runway 04/13 intersection. Both aircraft skidded for 110ft

http://www.airliners.net/open.file?id=0528176&WxsIERv=Orrpu%201900P-1&Wm=1&WdsYXMg=Havgrq%20Rkcerff%20%28Terng%20Ynxrf%20Nveyvarf%29&QtODMg=Dhvapl%20-%20Zhavpvcny%20%2F%20Onyqjva%20Svryq%20%28HVA%20%2F%20XHVA%2 9&ERDLTkt=HFN%20-%20Vyyvabvf&ktODMp=Abirzore%2019%2C%201996&BP=0&WNEb25u=Fpebttvaf%20Nivngvba%20-%20Qbht%20Fpebttvaf&xsIERvdWdsY=A87TY&MgTUQtODMgKE=Havgrq%20Rkcerff%20%2F%20Terng%20Ynxrf%20Syvtug %205925%2F5926%20gbbx%20bss%20sebz%20Puvpntb.%20Nf%20gur%20O rrpupensg%20jnf%20nccebnpuvat%20Dhvapl%2C%20gjb%20nvepensg%2 0jrer%20ernql%20sbe%20qrcnegher.%20Orrpupensg%20Xvat%20Nve%2 065-N90%20%28A1127Q%29%20naq%20Cvcre%20Purebxrr%20A7646W%20jrer% 20gnkvvat%20gb%20ehajnl%2004.%20Havgrq%20Rkcerff%20perj%20pb agvahrq%20gurve%20nccebnpu%20gb%20ehajnl%2013.%20Gur%20Xvat% 20Nve%20ubjrire%2C%20unq%20gnkvrq%20bagb%20gur%20ehajnl%20na q%20unq%20fgnegrq%20vg%27f%20gnxr-bss%20ebyy%20jura%20gur%20Orrpu%201900%20gbhpurq%20qbja.%20N %20pbyyvfvba%20gbbx%20cynpr%20ng%20gur%20ehajnl%2004%2F13%20 vagrefrpgvba.%20Obgu%20nvepensg%20fxvqqrq%20sbe%20110sg%20%2 8Xbqnx%20Fyvqr%20Svyz%29&YXMgTUQtODMgKERD=13466&NEb25uZWxs=2004-03-09%2000%3A00%3A00&ODJ9dvCE=&O89Dcjdg=HP-87&static=yes&width=1024&height=680&sok=JURER%20%20%28ZNGPU%20%28nvepensg%2Cnveyvar%2Ccynpr%2Ccu bgb_qngr%2Cpbhagel%2Cerznex%2Ccubgbtencure%2Crznvy%2Clrne%2C ert%2Cnvepensg_trarevp%2Cpa%2Cpbqr%29%20NTNVAFG%20%28%27%2B% 22pbyyvfvba%22%27%20VA%20OBBYRNA%20ZBQR%29%29%20%20beqre%20o l%20cubgb_vq%20QRFP&photo_nr=162&prev_id=0529496&next_id=0528145
http://www.airliners.net/open.file?id=0528145&WxsIERv=Orrpu%201900P-1&Wm=1&WdsYXMg=Havgrq%20Rkcerff%20%28Terng%20Ynxrf%20Nveyvarf%29&QtODMg=Dhvapl%20-%20Zhavpvcny%20%2F%20Onyqjva%20Svryq%20%28HVA%20%2F%20XHVA%2 9&ERDLTkt=HFN%20-%20Vyyvabvf&ktODMp=Abirzore%2019%2C%201996&BP=0&WNEb25u=Fpebttvaf%20Nivngvba%20-%20Qbht%20Fpebttvaf&xsIERvdWdsY=A87TY&MgTUQtODMgKE=Havgrq%20Rkcerff%20%2F%20Terng%20Ynxrf%20Syvtug %205925%2F5926%20gbbx%20bss%20sebz%20Puvpntb.%20Nf%20gur%20O rrpupensg%20jnf%20nccebnpuvat%20Dhvapl%2C%20gjb%20nvepensg%2 0jrer%20ernql%20sbe%20qrcnegher.%20Orrpupensg%20Xvat%20Nve%2 065-N90%20%28A1127Q%29%20naq%20Cvcre%20Purebxrr%20A7646W%20jrer% 20gnkvvat%20gb%20ehajnl%2004.%20Havgrq%20Rkcerff%20perj%20pb agvahrq%20gurve%20nccebnpu%20gb%20ehajnl%2013.%20Gur%20Xvat% 20Nve%20ubjrire%2C%20unq%20gnkvrq%20bagb%20gur%20ehajnl%20na q%20unq%20fgnegrq%20vg%27f%20gnxr-bss%20ebyy%20jura%20gur%20Orrpu%201900%20gbhpurq%20qbja.%20N %20pbyyvfvba%20gbbx%20cynpr%20ng%20gur%20ehajnl%2004%2F13%20 vagrefrpgvba.%20Obgu%20nvepensg%20fxvqqrq%20sbe%20110sg%20%2 8Xbqnx%20Fyvqr%20Svyz%29&YXMgTUQtODMgKERD=6858&NEb25uZWxs=2004-03-09%2000%3A00%3A00&ODJ9dvCE=&O89Dcjdg=HP-87&static=yes&width=1024&height=680&sok=JURER%20%20%28ZNGPU%20%28nvepensg%2Cnveyvar%2Ccynpr%2Ccu bgb_qngr%2Cpbhagel%2Cerznex%2Ccubgbtencure%2Crznvy%2Clrne%2C ert%2Cnvepensg_trarevp%2Cpa%2Cpbqr%29%20NTNVAFG%20%28%27%2B% 22pbyyvfvba%22%27%20VA%20OBBYRNA%20ZBQR%29%29%20%20beqre%20o l%20cubgb_vq%20QRFP&photo_nr=163&prev_id=0528176&next_id=0526114


http://www.airliners.net/open.file?id=0616183&WxsIERv=Obrvat%20747-151&Wm=0&WdsYXMg=Abegujrfg%20Bevrag%20Nveyvarf&QtODMg=Fgbpxubyz%20-%20Neynaqn%20%28NEA%20%2F%20RFFN%29&ERDLTkt=Fjrqra&ktODMp=Nhthfg%2019%2C%201986&BP=0&WNEb25u=Crgre%20Gnaperq&xsIERvdWdsY=A602HF&MgTUQtODMgKE=Gur%20747%20gnkvrq%20gur%20jebat%20gnkvjnl%20na q%20uvg%20n%20FNF%20QP9.%20cvp%20aoe%202&YXMgTUQtODMgKERD=30947&NEb25uZWxs=2004-07-09%2000%3A00%3A00&ODJ9dvCE=&O89Dcjdg=19779%2F40&static=yes&width=1024&height=693&sok=&photo_nr=53&prev_id=0614561&next_id=0616184
Northwest Orient Airlines: Boeing 747-151
Stockholm - Arlanda (ARN / ESSA)
Sweden, August 19, 1986
N602US (cn 19779/40) The 747 taxied the wrong taxiway and hit a SAS DC9.
More: Peter Tancred

You will need to approach the website for permission to use, of course. I have images in my collection but without provenance, PM if you wish.

[Golf Charlie Charlie]

What about the BKS Ambassador/BEA Trident collision at LHR around 1969 ? I am sure I have seen pictures of the aftermath of this event.

[treadigraph]

GCC, the BKS and Trident accident occured after the Ambassador left the runway and collided with several Tridents on stand - there is a photo of the damaged Tridents, though I haven't seen it in years or found it on line.

[ICT_SLB]

IIRC the Ambassador crash was caused by a horse getting its foot caught in one of the control wires. It was carrying a load of racehorses.

[gas path]

IIRC the Ambassador crash was caused by a horse getting its foot caught in one of the control wires. It was carrying a load of racehorses.
Actually found to be a failure of a flap actuator rod on the left hand side causing the a/c to enter an uncontrollable roll as the flap retracted.

[Brian Abraham]

Of any help?
http://www.faa.gov/RunwaySAFETY/ace/presentations/2.ppt