Spencer’s Story Part 2: as told by Critical Care Paramedic Ben
In part one of his story, former patient Spencer told us about the cycling accident that left him with two punctured lungs, and in urgent need of our advanced critical care. In part two, we hear from Critical Care Paramedic Ben, one of the crew members who was on-scene to treat Spencer that day.
‘I remember the incident well; it was a good flying day, and a nice day to be out on the bike. Working on shift with me that day was doctor Stewart – who is now our Medical Director. We flew with a brand-new pilot, Jim, on his first day flying Helicopter Emergency Medical Service (HEMS) – so he was supported by Pilot Dave, which meant two up front in the cockpit.’
‘Flying over the scene of the emergency there was an obvious, albeit tricky, landing site; a long, thin strip surrounded by tall trees and a slight slope. It was a challenging location for Jim’s first day on the job. Once we landed, Stewart and I piled out with our equipment bags and walked down the road a couple hundred metres to where Spencer’s accident took place.’
‘We put our kit down, and introduced ourselves to the ambulance crew on scene. It was then we realised that the paramedic on the ambulance was one of our senior critical care paramedics. He was doing a bank shift with South Central Ambulance Service (SCAS) and was able to give us a thorough handover with concise recommendations of his treatment plan for Spencer.’
Reflecting on the incident, Ben recalls the treatment given to Spencer:
‘We introduced ourselves to Spencer, who at this point was on all fours saying he couldn’t breathe and asking for help. He asked me how his bike was, and I remember telling him that it’s a good day, because it’s a new bike day! I seem to remember him laughing at that, but I’m not sure how much he would remember of that.’
‘At this point, we were getting a cannula into Spence and giving him strong painkillers. We gave him a decent amount of pain relief straight off the bat, just to make sure that he was as comfortable as could possible be, and so we could get him into a manageable position – we couldn’t do any further interventions with him on all fours.’
‘He was a patient that had what we call a ‘high GCS.’ GCS – or Glasgow Coma Scale – is a scale which aims to give a reliable and objective way of recording the state of patient’s consciousness. It’s measured up to a score of 15, with 15 being me telling you this story, fully cognisant. Spencer was a GCS 15, he was fully conscious. For him, that would’ve been a really hard job to deal with, as he was aware of what was going on and happening around him.’
‘Spencer had some extensive chest injuries – he had hit his chest against the A-pillar of the car and there was a decent amount of damage to the car. This was a serious injury with a big injury pattern. Spencer is a super fit guy, so the observations on his heart rate and blood pressure were reasonable. His body was doing well at maintaining itself. However, his oxygen saturations were low. The average person will have between 96% – 98%, people with chronic lung problems might have it at 90%. Spencer’s was in the low 70s, like someone who might be at extreme altitude such as climbing Mount Everest. He was really struggling; his respiratory rate was really high and he was in significant pain.’
‘We decided to give Spencer strong pain relief, do the anaesthetic, and then we would give him what are called ‘finger thoracostomies,’ a surgical intervention on either side of his chest to decompress what is called tension pneumothorax. In layman’s terms, a pneumothorax is described as a punctured lung. He had what’s called a surgical emphysema, when air is leaking out of the chest and gets under the fatty tissue of the skin. He was in a considerably bad was in terms of his injuries, so we gave him anaesthetic and began the process of ‘lung recruitment’ – getting the lungs to work properly.’
‘It took quite a long time to get Spencer to be saturating oxygen at a point where we were happy. We had got his ventilation strategy correct. We had to re-finger the thoracostomy, where you put the finger back into the surgical incision to release air. We were having to do that on multiple occasions, every couple of minutes, to release the trapped air and stop his lungs re-tensioning so that we could keep him stable.’
On the 3rd September 2020, the charity kicked-off it’s 21st Anniversary celebrations by welcoming Her Royal Highness The Countess of Wessex and former patients to socially-distanced meet and greet with the crew. For paramedic Ben, it was the perfect opportunity to catch up with Spencer.
‘Spencer has gone on to complete an amazing bike ride a year to the day after his accident, an incredible feat of fundraising for Thames Valley Air Ambulance; It is a testament to him as an individual, and as an athlete.’
‘Meeting patients can give a sense of resolution. I think because on-scene there was definitely the potential for Spencer not to survive in my mind, when I did find out that he had gone on to make an amazing recovery – and was back out cycling – it was amazing to hear. Because I am a cyclist, it was a call-out that was quite close to home – I often tank down a hill at 30mph plus. What happened to Spencer could have easily happened to me as well.’
‘It’s a relatable injury, and the fact that he’s gone on to do fundraising work for the charity is just incredible. As a relatively new critical care paramedic, it was one of the jobs that will stick with me for the rest of my career.’
Join the community by signing up and keep up to date with news and events.
Privacy & Cookies Policy
These cookies remember choices you have made on our website in order to improve your experience. This could include your username, language or the region you are in. The information these cookies collect may be anonymised and only apply to your browsing activity on our website.
This cookie monitors which event pages the user has visited, in order to provide them a list of recently visited event pages. This cookie is only used to improve the user's experience of our website.
This cookie monitors which web stories the user has read, in order to provide them a list of recently read stories. This cookie is only used to improve the user's experience of our website.
These cookies collect information about how you use our website, for example which pages you most frequently visit, or if you receive error messages. These cookies don’t collect any information that could identify a visitor. The information collected by these cookies is aggregated and therefore anonymous. They are only used to improve how our website works.
This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
This cookie is used by Google Tag Manager to store and track website conversions.
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form.
This cookie is used by Hotjar to detect the first pageview session of a user. This is a True/False flag set by the cookie.
This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
This cookie is set to let Hotjar know whether a visitor is included in the data sampling defined by our site's pageview limit.
This cookie is set to let Hotjar know whether a visitor is included in the data sampling defined by the website's daily session limit.
This cookie is set by HotJar. When the Hotjar script executes they try to determine the most generic cookie path to use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, HotJar try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
5 months 27 days
This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.
This cookies is set by Youtube and is used to track the views of embedded videos.
These cookies collect information about your browsing habits to make advertising relevant to you and your interests.
This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin.
1 year 24 days
Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.