translate a1180 crash card

Discussion in 'Research Material' started by Stuart3009, Apr 17, 2022.

  1. Stuart3009

    Stuart3009 Active Member

    can anyone translate or put into non aviation english a crash card a1180 as ive been contacted by relative of a pilot who was killed at raf culmhead and the crash card ive got i cant read it
     
  2. RAFCommands

    RAFCommands Senior Member

    Yes - but sight of it or some clue to accident is somewhat a requirement.

    Ross
     
  3. Stuart3009

    Stuart3009 Active Member

    Here is crash card
     

    Attached Files:

  4. RAFCommands

    RAFCommands Senior Member

    This is the F1180 for Spitfire MH822 flown by F/Sgt I F Hakansson 1575089 of No.165 Sqn who was seriously injured when he collided on landing with Spitfire MH796, killing it's pilot F/O E H Francis 136019 on 20th Jan 1944.

    The rear of the card, which you posted, has the summary of evidence and Court of Enquiry finding written out.

    Which part or words are the problem - to save me transcribing the whole card and repeating what you already know/understand about the incident.

    Ross
     
  5. Stuart3009

    Stuart3009 Active Member

    hi Ross

    many thanks for this ok so I know I’m asking alot I would love all of it translated what it’s a relative of the pilot that crashed ref on this card has contacted me regarding his grandfather who was the pilot and I want to give him an idea what happend

    if it’s possible my private email is rafculmhead@gmail.com
     
  6. RAFCommands

    RAFCommands Senior Member

    I've previously done a chapter and verse translation of Form1180 for you here

    A180 CRASH CARD

    Almost all the section explanations apply here as well so use what I have previously transcribed and explained for you as a starting point.

    Full and clearer images of F1180 attached to this. Credit any use to RAF Museum and WW2Talk
    Front Page:
    Form 412 Court of Enquiry carried out - no AiB investigation ordered
    Hollerith edge codes correspond to included information in boxes

    Rear Page:
    LCA - Landing Collision Aircraft - Spitfire 822 collided with 796 on landing. Invest:

    PCL - Pilot Collision Landing - Pilot showed insufficient care in overtaking - collided with other a/c (aircraft - Ross) when ldg (landing - Ross) with 10/15 MPH tail wind. Failed to make sure that parts of runway clear.

    XCA and XA - External influences Collision Aircraft and External Influence of Aircraft (the collision was a factor as well as the other aircraft - Ross) - 796 after landing went to centre of runway and taxied slowly 5 MPH instead of clearing runway.

    Court of Enquiry
    Landed too far up runway on sboard (starboard - Ross) side and then ran towards centre, overtaking 796 striking his tail with wing causing a/c to slew together prop (propeller - Ross) of 882(sic - Ross) slashed through cockpit of 796 killing pilot. OC (Officer Commanding - Ross) concurs. AOC (Air Officer Commanding - Ross) concurs. AOC-C (Air Officer Commanding in Chief - Ross) both pilots contributed to accident. No discip (disciplinary - Ross) action.

    I would struggle to put the card into a simpler description.

    Ross
     

    Attached Files:

    Last edited: Apr 19, 2022
    Owen likes this.
  7. Stuart3009

    Stuart3009 Active Member

    Thanks Ross
     
  8. Stuart3009

    Stuart3009 Active Member

    hi ross

    sorry to ask but ive contacted raf hendon for crash card for mh796 and they said they dont have one do u know reason why
     
  9. RAFCommands

    RAFCommands Senior Member

    It's a joint card indexed under MH822 - see the front of the copy I posted.

    Ross
     
  10. Stuart3009

    Stuart3009 Active Member

    oh i see so what have they only got one pilots name not 2 as the relatives wants to know
     
  11. RAFCommands

    RAFCommands Senior Member

    As I said on the other thread:

    "RAF Aircraft Accident Cards were really only a quick handy reference for the Clerks to find other documents in the RAF Registry and to track progress of any investigations."

    In this case the Casualty File contained the detail of both personnel injured/killed, Form 765(c), Signals T104 and T105, File G42778 as well as Form 412.

    Ross
     
    Last edited: Apr 21, 2022
  12. Stuart3009

    Stuart3009 Active Member

    Hi Ross

    me again sorry but you are only person that’s been so helpful to piece together the crash card the relative has asked me any idea if it states on crash card which runway this happend on
     
  13. RAFCommands

    RAFCommands Senior Member

    Not on Form 1180 - I have to say again this is only an index card - this type of detail was in the supporting files - which at the time the card was created were easily accessible in the registry.

    You can try to guess from surviving met data for the day, time and place. But as the aircraft were landing out of head wind it could have been on any of the crosswind runways rather than one associated with the downwind direction.

    All this is supposition - the only accurate way is to access the surviving Registry files in their archive locations.

    Dave has shown you where to get the ORB - Summary of Events Form 540 and Record of Events Form 541 - The 20/1/44 entry on Form 540 contains more detail of F/O Francis time at the Squadron than normal for ORB scribes.

    Again, as I said on earlier threads the Station will also have an ORB at the TNA but this will not have been digitised yet so will need personal inspection to see what it says about the incident.

    Best route for the detail the relative seems to want is for them to apply for both F/O Francis Service Record £30 (use the online method - return is between 4 to 6 weeks at the moment) and an additional paper format application to RAFAHB £30 to request a copy of the Casualty File (this may still be with the MoD and accessible to them or it may be in the process of redaction where the MoD will not be able to access it).

    Request information held on the RAF Casualty Files

    Ross
     
    Last edited: Apr 23, 2022

Share This Page