\n<\/p>\n
If I\u2019m being specific about the moment it clicked, it was reading a paper called \u201cOn the Role and Challenges of Computational Fluid Dynamics (CFD) in the Aerospace Industry\u201d by two Boeing engineers, P. R. Spalart and V. Venkatakrishnan.<\/p>\n<\/div>\n
It was written from the perspective of engineers working in the aerospace industry, and I found their discussion of how far CFD had come and how much was still unsolved interesting. Turbulence modelling, computing power, grid accuracy, all of it. I remember finishing it and just thinking, okay, this is what I want to spend my time on. Add Cranfield\u2019s name in CFD circles into the mix and the decision made itself. I had the first international flight of my life coming to Cranfield, mind you I stood in the wrong immigration line at first.<\/p>\n
Once I got here, the course covered far more than I expected: computational methods, programming, CFD, structural analysis, CAD, the whole spread. My favourite by far was the CAD Airframe module. There\u2019s something quite satisfying about actually building an aircraft\u2019s geometry instead of just simulating one someone else made, it finally connected the design side and the analysis side for me in a way lectures alone hadn\u2019t.<\/p>\n
\nThe C++ and Computational Methods assignment, on the other hand, nearly broke me a couple of times, but it\u2019s the one I learned the most from. You stop taking the software for granted once you\u2019ve written the numerical methods underneath it yourself.<\/p>\n<\/blockquote>\n
Then there\u2019s my thesis, which has quietly taken most of my year. I\u2019m modelling fuel sloshing and pressure behaviour in aircraft wing tanks, the idea being to inform where fuel level sensors should actually sit. I built an automated Python based CFD workflow for it and spent a lot of time picking apart multiphase flow under different conditions. It\u2019s the one project where CFD, coding and proper aerospace engineering all had to come together at once, which is exactly the kind of problem I came here for. I owe a lot of my learning here to Dr. Tom Teschner, from his first mail to me with the offer letter attached to it to his lectures and supervision of my thesis really shaped me into a better engineer.<\/p>\n
\nOutside of coursework, I had the opportunity to fly in a Saab aircraft as part of my course, and my stomach absolutely dropped when it pitched down. Small moment, but it\u2019s stuck with me.<\/p>\n<\/blockquote>\n
If I\u2019m honest, though, what I\u2019ll remember most isn\u2019t just academics at all. It\u2019s the people here. Cranfield pulls in students from everywhere, and some of the best friends I\u2019ve made here are from countries I\u2019d barely visited before. I also experienced my first snowfall here that was a magical moment for me. Got to represent the university in the IMechE UAS Challenge 2026, working on an unmanned aircraft project with a small team, which was a good reminder that engineering rarely happens alone in a room.<\/p>\n
Looking further ahead, I want to do a PhD in materials science, focused on composites. It wasn\u2019t the plan when I arrived, it grew out of how much I enjoyed the composite airframe side of things here. I had worked with balsa and carbon fiber before coming here but after learning the advanced modelling and manufacturing techniques, I want to dive in to find more about it.<\/p>\n
So, if you\u2019re weighing up whether to come to Cranfield, my honest advice is: don\u2019t wait until you feel ready. You won\u2019t, not fully, and that\u2019s fine. Ask the obvious questions, give yourself room to catch up on the bits you don\u2019t know yet, and say yes to things outside your course whenever you can. A lot of what I\u2019ll actually remember didn\u2019t happen in a lecture hall.<\/p>\n
Find out more about the Computational Fluid Dynamics MSc<\/a><\/em>\u00a0at Cranfield University.<\/em><\/strong><\/p>\n<\/div>\n