Aircraft Design Projects Episode 13 pot

“chap11” — 2003/3/10 — page 341 — #11 Design organisation and presentation 341 5.3       It may be used to present web addresses and data sources, considera- tions for future main agenda items, or short reports requesting extra information or data (that could be available within 24 hr) from the group members.       Etc. 6. Details of the next meeting of the group (This records the decisions taken at the end of the meeting on the date, time, venue of the next meeting and any subsidiary meetings that have been arranged.) Meeting ended at 1845 hr! Name of secretary Date of issue 11.3.3 Dispersed meetings Most of the meetings that are held for academic work will involve group members meeting face to face in their college department. Some design courses run a group project in which it is not possible for the team to meet in this way. For example, some members may be in different colleges or universities, or even in a different country. In this case, the meeting format may involve teleconferencing or some other form of electronic communication. Such meetings may be fun at first due to the unusual nature of the interaction, but there are several safeguards that must be followed in order to avoid confusion. Some of these difficulties arise from the remoteness of the contributors, some from the instant response of the communication system, and some from cultural differences. For example, it is sometimes not possible to pick up non- aural clues when members are making suggestions (was he being sarcastic or serious?). Everyone has experienced sending an email response too quickly and then regretting the consequences. Even time zone differences and course programme variations can lead to confusion and disruption. All of these difficulties are surmountable with a little care and patience in the management of the meetings. It is even more essential to follow the conduct of meetings described above for such meetings. 11.4 Writing technical reports The ability to write a clearly understood, concise, and accurate technical report is regarded as a principal requirement of a professional engineer. You will be judged in your career by your skill at producing high-quality and readable reports of your work. You probably have all the ability necessary to do this but our experience has shown that students need to be informed of the procedures and characteristics that are common to technical writing. The notes below describe the features found in a good technical report: • It has a neat presentation in both appearance and language. • It is easy for readers to ‘navigate’ the contents to find the information they seek. This requires careful attention to page numbering, references in the text to each figure “chap11” — 2003/3/10 — page 342 — #12 342 Aircraft Design Projects and appendix (these need to be numbered) and clear identification of the source of any external material pertinent to the content of the report. • It is written in a language that is impersonal (mainly in the third person). A technical report is not a narrative. Therefore, there is a difference in the language you use between a letter home and a report to your supervisor! • Although the specific points mentioned above need to be taken into account the main criterion of a well written report (to the intended readership) is that it is – interesting. You are not the first person to write such a report. There are many good examples available for you to follow. Textbooks, company reports, research papers, and good quality aeronautical journals provide adequate evidence of good practice. The most annoying faults that are found in student work relate to avoidable ‘typos’, missing labels (e.g. figure and table numbers), out of sequence pages, duplicate pages and references, and figures that cannot be found. Mostly these deficiencies arise due to the shortage of time allowed to adequately proof-read the final version. The handing- in time should not be assumed coincident with the final printing and collation of the report! The sections below bring together advice on the production of the report. 11.4.1 Planning the report Before starting to write the report, make sure that you can answer the following questions: • What is the objective of producing the report? What use will the readers make of the report? What material has to be included in the report? Have you been made aware of any criteria to be used if the report is to be assessed? • Who will read the report? Are you aware of what they are expecting to see in the report? Have they infor med you of the purpose to which they will use the report? What experience in the subject matter of the report do they possess? What prior knowledge do they have that is pertinent to the content of the report? • How much time is available for you to write the report? What length should it be? Are there any formatting criteria that must be met? 11.4.2 Organising the report This involves listing the topics that you want to include. The report must have a logical progression. It starts with an ‘introduction’ section. This is followed by the ‘main body’. The report is completed by a ‘termination’ section. The topics should be grouped and allocated to one of the sections. These groups should be titled with appropriate headings. A smooth transition between groups of text in the report must be provided. The start of the report establishes the relevance of the work and puts your findings into context by identifying other relevant studies/information. This is usually followed by an overview of the structure of the report. This describes the progression of the work and any subsidiary information. Do not assume that the reader is familiar with your design problem even if the report is to be read only by your design instructor. The ‘main body’ contains the detail design work covered in the report. The nature of this section will vary depending on the purpose of the report. For example, it could contain the methods of analysis used in the design work, explanations of the theories used and any assumptions that have had to be made. It will describe the results that have “chap11” — 2003/3/10 — page 343 — #13 Design organisation and presentation 343 been found and how these results can be interpreted relative to the study objectives. Obviously, this could involve a substantial amount of text and several figures. Tomake it easier to read it is advisable to subdivide the section (e.g. mass estimation, aerodynamic analysis, propulsion, performance, etc.). Avoid unnecessary padding (e.g. extractions from textbooks and the Internet). Try to be concise but make sure that the reader, who is not as familiar with the work as you, can understand what you have done. To finish the report you should summarise the main design features, make observa- tions on the results, draw conclusions (this may involve making relevant comparisons with competitor and other aircraft) and finally make some recommendations. No new material should be brought into the termination section. Several ‘administration’ sections sandwich the three main textural sections. These include: (a) prior to the introduction section: • title page • abstract or executive summary • contents list • notation and list of symbols (b) after the termination section: • list of references • bibliography • figures • tables • appendices A typical report layout is shown in Figure 11.2. 11.4.3 Writing the report The sequence in which the report is written will not be in the same order as it is collated in the finished version. For example, the abstract/executive summary is usually the last section to be written. Write each section separately but ensure that the style and format are consistent throughout the report. If you are working in a group, it is possible for separate individual members to write different parts. This will require decisions to be taken on the appearance of the report. When using word processing software, this is achieved most easily by designing a ‘format template’ that each writer uses. Ensure that the report is readable by following the suggestions below: • Avoid conversational language (especially colloquia, jargon and slang). • Avoid the use of undefined acronyms and technical terms unfamiliar to the reader. • Use an impersonal style (e.g. ‘it was found that ’, not ‘we found ’). • Keep sentences short and to the point, the language style precise, and the report concise. • Use paragraphs to group descriptions, reasoning, and thoughts together. Do not use them just to space out the text. • Try to avoid repetition except when summarising your previous findings. • Avoid using ‘fancy’ fonts and too many textural, format changes. • Use a ‘serif’ text font (e.g. Times) for the main text passages, as this is easier to scan-read. Use a ‘san serif’ font (e.g. Arial) for headings. • Avoid font sizes of less than 10pt for A4 or American 8.5 in × 11 in paper. • Avoid colour if the report is to be photocopied or printed. “chap11” — 2003/3/10 — page 344 — #14 344 Aircraft Design Projects Title page Exec. summary Contents Notation Introduction (Literature review) Main body Recommendations References Tables Figures Appendix A Appendix B Appendix C Conclusions Fig. 11.2 The full report Before you start the report decide the hierarchical structure of your headings. Select progressively fewer prominent styles and sizes for lower order headings. 11.4.4 Referencing Using text, figures, diagrams, data, photographs (etc.) from sources other than those produced by you or your group (e.g. textbooks, industrial reports, technical journals, the Internet, etc.) and not correctly indicating the origin is called: PLAGIARISM Apart from this being against the law (e.g. infringement of copyright), it is regarded as professional cheating. It could lead to your career suffering and possibly result in exclusion from your professional body. Referencing and displaying the source of external information is your only ‘insurance policy’ against an accusation of plagiarism. Correctly referencing any material used in the study and quoted in your report adds validity to your work. It also indicates that you are familiar with the area of study and have spent time and effort researching the field. Assessors will penalise you heavily if “chap11” — 2003/3/10 — page 345 — #15 Design organisation and presentation 345 you, intentionally or not, omit to quote sources (the Internet included). They are likely to give you credit if you demonstrate your knowledge of the subject area. There are several different methods of showing the source of external material. For some reports the method of referencing is prescribed by the recipient. When including a substantial extract in the report (more than a few words), it is common practice to put it in quotation marks and/or change the text style (often to italic) to distinguish it from the original text. If you are using extensive extracts from an external source, it is advisable to obtain written permission from the author or the copyright holder. They may require you to fully credit them at the point of insertion. When referring to external work, it is usual to add an indicator (a number) in the text and to provide a full reference to the original text in a reference section towards the end of the report. Alternatively, the full reference can be added as a footnote on the page containing the indicator. The full reference must contain sufficient detail to allow the original to be located in a library or on the Internet. Most textbooks (including this one) and other technical reports will provide you with examples of the correct for mats for writing the full reference. For visual material (diagrams, graphs, photographs) it is normal just to quote the source in the caption but i f several are used from one source it is necessary to apply the full referencing method. 11.4.5 Use of figures, tables and appendices Without a link in the text, a figure, table or appendix should not be included in the report. Figures, tables, and appendices should be numbered separately and sequentially (e.g. Figure 9.5, Table 2.3, Appendix 3). The numbering order should coincide with the order they are introduced into the text. Each figure should be titled and listed in the contents section of the report. The word ‘figure’ is used for any visual representation. Do not use words like ‘sketch’, ‘graph’, ‘plot’, ‘photograph’, ‘plate’, ‘drawing’, ‘illustration’, ‘diagram’ as a caption; they are all termed figures. All figures and the text appearing on them must be readable from the bottom edge (portrait) or the right-hand side (landscape). Remember to leave space around the figure to allow for binding. When electronically inserting figures or scanned material, avoid distorting the image. If the figure is to be reduced for insertion in the text, make sure that the original is sufficiently bold to avoid unreadable text and lines when made smaller. Be aware that some standard templates available on widely used drawing and graphing software are not suitable for direct insertion into technical reports. Drawings gener- ated by several popular CAD programs, which look very good on the computer screen, sometimes virtually disappear when inserted into standard word processing applica- tions. Colours that appear brilliant against another colour background in a computer graphics presentation will fade into oblivion or become indistinguishable from other hues in print. Graphs will need modifying as suggested below, especially if the report is to be printed in monochrome: • Avoid the use of colour on the graph, particularly as a background to the plotting area. • Distinguish lines either by using different line types (solid, chain, dashed) or by applying different line markers. • Indicate suppressed zeros on the axes. • Select a text format that is consistent with the report style. • Make sure that the text is not too small (or too large). • Apply gridlines to both axes, or neither. “chap11” — 2003/3/10 — page 346 — #16 346 Aircraft Design Projects • Ensure that the axes have number divisions that can easily be measured. The reader may want to scale a point from your graph so provide a scale that you would like to use if you needed to do this. • Quote units on each axis and provide annotation for the line markers. • Title the graph in the same format as used for other figures (normally placed below the graph). • Preview the figure or table before printing to make sure all the details are visible and clear. In most software packages it is possible to create a template that matches the format specification of your report. Large amounts of detailed analysis and/or data can be removed from the main text and put into separate appendices. This avoids an interruption to the ‘flow’ of the text. In such cases, the report must be capable of being understood, without reference to the detail in the appendices. This may mean that the main results from the detailed work will need to be added to the main text. The appendices should be regarded as supplementary to the report. They are there to allow the reader to clarify any confusion that arises from the results in the main text. 11.4.6 Group reports When working as a design team, individual members will be ‘expert’ in different spe- cialised subject areas (e.g. structures, aerodynamics, flight simulation, etc.). This may mean that the work done in each specialisation is reported by the team member respons- ible for that subject. This approach may lead to some difficulties if the production of the report is not carefully controlled and managed. Here are some guidelines to avoid such problems: • It is important to decide, within the limitations of the length of the report, what subjects/topics should be included. Each specialist may feel that his or her work is more significant than other members’ work. It will be necessary to agree what is the best overall composition of the report to meet the objective. Compromises will need to be agreed before individuals start writing their input (see comments below about individual assessment reports). • Although it may be common practice to compose the table of contents after the report has been written, it is worthwhile drafting this at the start. This helps to succinctly define the nature of the report. It can act as a list of sections to be written and as an action list that defines the names of authors of various sections and when their contributions are required. • One of the best ways of selecting the content of each section is to identify and agree what ‘key’ figures should be included. • As mentioned above, the group must decide the design of the report style and set this into a template that each writer will use. • When several different people are independently writing technical analyses, it is important that the nomenclature is agreed (e.g. will M be used for mass, moment, or Mach number, etc.?). • The group report will not be satisfactory if it is composed from ‘cut and paste’ extracts from individual specialist reports. The group report must be created as a totally separate entity. This will require the specialists to précis their more extensive individual reports. Only the main findings and conclusions will be required for the group report. “chap11” — 2003/3/10 — page 347 — #17 Design organisation and presentation 347 • Assign a subgroup who is not too involved with the production of the report to act as proof-readers and editors. For this task to be effective, they will need time to thoroughly review the finished report. This will mean that time must be allowed in the production schedule for this to be done and to allow any changes that they recommend being included in the final version. • The figures to be included must be in a standard format. This may be most easily achieved if a subgroup of students, who are not involved in writing the text, is made responsible for this work. Throughout the design process it will have been necessary to progressively improve the detailed analysis of the aircraft to gain confidence in your predictions. In group work, this will have involved individual members of the team performing analysis in various specialist areas. The group will require verbal and written reports from these ‘experts’ as the design unfolds and decisions are taken on the aircraft configura- tion. These individual reports will form the basis of specialist reports to be submitted at agreed milestones in the project development. These reports will contain figures and data that will be required for the final group report. These figures and data will form the basis for the descriptions to be included in the main body of the final group report. 11.4.7 Review of the report When the report is complete, it is worth answering the following questions to make sure that you have not overlooked anything that is important: • Is the report presentable? Are you pleased with the way it looks? Does it look ‘pro- fessional’? How does it compare with the reports that you used as examples of good practice? • Does it accurately present your understanding of the problem and your abilities in finding a solution to the original problem? • Does it show an imaginative and fresh approach to the problem? • Does it match your original intentions? • Is it understandable to the people who will be reading it? • Will it meet the expectations of the assessors? (Do you know what these are?)For example: – Does it demonstrate a thorough understanding of the problem (e.g. aircraft oper- ational requirements, external threats to a successful outcome, risk assessment, and potential for development)? – Have you clearly described the technical approach that you have adopted? – Have all the theories and data used in the design been correctly applied and validated against known information? – Have you identified the critical technical problem areas and offered potential solutions to these difficulties? – Have you covered all the factors that the assessors will be expecting? Figure 11.3 shows an example of a contents list taken from a student final, aircraft design, group report. “chap11” — 2003/3/10 — page 348 — #18 348 Aircraft Design Projects This was the format of a report to the NASA ÂUniversity Design CompetitionÊ in 2002. The competition required a short (20 page) report supplemented with a series of detailed specialist reports (in appendices). The aircraft was a personal (two-place) very short take-off and landing vehicle with a new type of engine and twin ducted fans. TABLE OF CONTENTS TABLE OF CONTENTS Team members Abstract Executive summary 1. Project description 2. Aircraft specification 2.1 Introduction 2.2 Performance 2.2.1 Takeoff and Landing 2.2.2 Cruise Performance 2.2.3 Climb and Turn Performance 2.2.4 Performance Comparison 2.3 Propulsion 2.3.1 Rand-Cam Engine 2.3.2 Engine Installation 2.3.3 Ducted Fans 2.4 Aerodynamics 2.5 Stability and Control 2.6 Structures 2.6.1 Structural Design Aspects 2.6.2 Structural Overview 2.6.3 Landing Gear 2.7 Avionics and Systems 2.7.1 Avionics 2.7.2 Systems 2.8 Ergonomics/Human Factors 2.9 Manufacturing 2.10 Cost 2.11 Practical Applications 3. Small Aircraft transportation systems (SATS) 4. Student work schedule Appendix A: Competition information Appendix B: Aircraft performance Appendix C: Propulsion Appendix D: Aerodynamic analysis Appendix E: Stability & control Appendix F: Weight & balance Appendix G: Structures Appendix H: Avionics & systems Appendix I: Cockpit layout Appendix J: Manufacturing issues Appendix K: Cost analysis Appendix L: Design selection process Fig. 11.3 Example content list (group design report) 11.5 Making a technical presentation There is a fundamental difference between making a technical presentation and giving an after-dinner speech! Although in both a friendly and relaxed approach is expected, it is not advisable to be too flippant or risqué in a technical talk. Since your audience will be looking at you, it is important that your appearance should be in keeping with the importance of the occasion. In a team presentation, the members should agree in advance on a dress standard. Be well groomed and smartly dressed but do not take this to an extreme, as this will also be distracting. The intention is to appear professional and to display confidence in your subject. Try not to shuffle papers prior and during “chap11” — 2003/3/10 — page 349 — #19 Design organisation and presentation 349 your speech. Look towards the audience as much as possible so that they feel you want to involve them in your experience. Try to avoid standing between your audience and the projection screen or between the projector and screen. The sections below give advice on the preparation and presentation of the talk. 11.5.1 Planning the presentation There are four questions that you should answer before starting to prepare the talk: • What is/are the reason/s for making the presentation? For example: – to present information – to display your abilities – to explain your methods of study and results – to explain your decisions – to persuade people – to sell your ideas, or yourself • Who will be in the audience and what experience do they have of the work you are presenting? For example: – What is their technical knowledge? – What are their motives for being at the talk? – What are they expecting to gain from the talk? – Do they have any specific requirements of which you know? • How much time is available for the presentation? – Knowing this, you can divide the time into segments to suit the material to be presented. – Do not attempt to get too much detail into a short presentation. – Make sure that you do not overshoot your time. – Do not try to get too many slides into your presentation (see later advice for timing of each slide). • How many separate topics can be covered in the allowable time? – Too many and each topic will appear to be shallow. – Too few and some important detail will need to be left out which will make the presentation appear to be shallow. 11.5.2 Organising the presentation Organising the presentation will require you to: • Provide a logical progression to the talk. • Divide the talk into clear segments, each with a specific objective. • Start by establishing the relevance of the talk to the audience. • Make sure that, in the main body of the talk, you have smooth and logical transitions between each segment. • Finish with a summary of your work making recommendations that lead from your results. The opening and closing sections are the most important parts. Initially you need to get the attention of your listeners and finally leave them with something to remember your work. In the opening set the style of your talk by engaging the audience with eye contact, relaxed body language and airs of confidence in what you are about to tell them. Speak clearly and not too fast. Make sure you can be heard and understood at the back of the room. At the end of the talk, bring your audience into your work by “chap11” — 2003/3/10 — page 350 — #20 350 Aircraft Design Projects making comparisons with which they will be familiar. Describe future considerations and at the end throw down a challenge. Finally, do not be afraid to ask if they have any questions. 11.5.3 Use of equipment In our modern high-tech environment, you need to make a careful choice of equipment to use in your presentation. Your choices will usually include: • Overhead projector (OHP). • Slide projector. • Computer software (e.g. Powerpoint) and projection. • Video/DVD. Students sometimes feel tempted to use several different methods in their presentation in order to ‘jazz up’ their talk and demonstrate their abilities at handling equipment. Experience has shown that this is a very hazardous strategy. The favourite habitation of gremlins is in visual demonstration equipment. They know their mischief here can cause the most chaos. The best advice is to keep the presentation as simple as possible and to have a back-up strategy available in case of equipment failure. Here are some tips: • Back up all your files and take these with you to the presentation venue. • If you are taking your own equipment to the venue, know what you will do if/when it fails. • If you are intending to use equipment supplied at the venue, ensure that it is com- patible with your files, tapes, etc. Note that European and US video systems are different, PC and Apple operating systems are different, and not all computers have the same versions of standard operating systems and software. • Well before you are scheduled to give your talk go to the presentation room to install your equipment, to try out the provided equipment and to practise your talk. • Always have a ‘back-up’ set of overhead slides for use should computer presenta- tion fail. If you intend to change the method of presentation during your talk (e.g. showing a computer simulation of your aircraft flying), this will take extra time from that allocated for your presentation. It will also interrupt the audience concentration in your talk. The value of adding the item to the talk must be considered against these disturbances. For aircraft design presentations, it is not often necessary to introduce dynamic (video) clips. If available, these may be held in reserve to show to interested participants during the question time or later. On the other hand, for a long presentation (i.e. more than 50 minutes) changing the presentation method will help keep the audience awake. A technique along these lines is simply to stop using visual equipment for a short time (e.g. turn off the OHP). This will refocus the attention of the audience onto the speaker. However, be careful not to use these tricks too often. As mentioned above, the best presentations are intentionally kept simple. This strategy also applies to the use and design of the visuals. Here are some more tips: (a) OHP: • Know the purpose of displaying each slide in your talk. • Make sure that all the slides are in the same format so that they appear as a set. • Keep the slide ‘crisp’. For scanning or reading pages of text a serif font, like Times, is good but for displayed text a san-serif font, like Arial, is easier to read [...]... units of measurement 360 Design assessments 353 Design concepts: Amphib aircraft 312 Biz jet 57 Flying car 158 HALE aircraft 278 Mil bomber 210 Mil trainer 110 Design considerations 39 Amphib aircraft 312 Flying car 177 HALE aircraft 275 Design course aims 353 Design flexibility 3 Design flowchart 7 Design meetings 338 Design organisation 10 Design presentations 349 Design process 1 Design requirements:... Aircraft empty (basic) mass 20 Aircraft noise, Mil bomber 206 Aircraft operational empty mass (OEM) 20 Aircraft price: Biz jet 81 flying car 198 Aircraft requirements 12 Amphib aircraft 312 HALE aircraft 272 Mil trainer 103 Aircraft speed definitions 359 Aircraft speed envelope, HALE aircraft 287 Aircraft structural mass 20 Aircraft systems, flying car 197 Airworthiness 13 Alternative fuselage layouts,... your aircraft 356 NASA/FAA Gen Av Design Comp 178, 325 Nemesis racing aircraft 151 Non-technical considerations 39 Northrop Grumman Global Hawk 277 Observables, Mil bomber 205 Observation geometry, HALE aircraft 273 Observation range, HALE aircraft 273 Operation on water, Amphib aircraft 317 “index” — 2003/3/10 — page 369 — #3 369 370 Aircraft Design Projects Operational experience 12 Organising design. .. Amphib aircraft 318 Biz jet 75 Elec racer 162 flying car 186 HALE aircraft 298 Mil bomber 217, 234 Mil trainer 117 Aerodynamic, component parasitic drag: Mil trainer 117 Biz jet 75 Aerodynamic, lift induced drag, Biz jet 75 AIAA Student Design Competition 203 Aircraft balance 21 Amphib aircraft 319 HALE aircraft 297 Mil bomber 233 Aircraft development programmes 15 Aircraft development, Biz jet 54 Aircraft. .. without too many formulae, how aircraft work and what are the operational and flying characteristics It presents a good overview of aircraft and aircraft design Stinton, D., The Design of the Aeroplane, Blackwell Science Ltd, 1983, ISBN 0-63201877-1 In this book, Darrol Stinton presents the formula and detail design data for aircraft design It has good information on the light aircraft sector and many unusual... reports and books on aircraft subjects The best known is Janes’ All the World’s Aircraft which is published annually and contains technical information on most types of aircraft They also publish books such as Whitford, R., Design for Air Combat (1989) Reference books Useful reference books for aircraft projects include Janes’ All the World’s Aircraft, mentioned above, and Brassey’s World Aircraft and Systems... Hawk aircraft 102 Baseline aircraft drawing: Amphib aircraft 325, 326 Biz jet 68 flying car 185 HALE aircraft 306 Mil bomber 216, 228, 231 Mil trainer 114, 135 Baseline aircraft evaluation 19 Baseline aircraft revision 31 Baseline configuration 6 Baseline general arrangement, Mil bomber 264–5 Blended body layout, Biz jet 61 Blended delta layout, Mil bomber 212 Braced-wing layout: Biz jet 59 HALE aircraft. .. application of the methods to civil aircraft design Detailed data on aircraft, engines and airports can be found in the web pages associated with this book Mattingly, J D et al., Aircraft Engine Design, AIAA Education Series, 1987, ISBN 0 930 403 23 1 Along with G C Oates’ book in the same series this is the best book on engine design for performance and engine /aircraft integration The format of the... Unfortunately there are no example projects included but the book has stood the test of time and is still widely appreciated Raymer, D P., Aircraft Design: A Conceptual Approach, third edition AIAA Education Series, 1999, ISBN 1 56347 281 0 An excellent book, describing in detail the fundamental principles underpinning the initial design of aircraft This book is the most popular aircraft design book used in undergraduate... Initial sizing 15 Mil trainer 112 Amphib aircraft 313 Biz jet 62 Elec racer 156 HALE aircraft 283 Mil bomber 213 Innovation 9 International Standard Atmosphere (ISA) 359 Internet searches 366 IR, Mil bomber 204 ISA 359 Joined-wing layout, HALE aircraft 280 Life cycle costs (LCC) 8 Lift to drag ratio 18 Lift to drag ratio, Mil trainer 116 Lockheed U2 aircraft 271 Making design presentations 349 Manoeuvre . from a student final, aircraft design, group report. “chap11” — 2003/3/10 — page 348 — #18 348 Aircraft Design Projects This was the format of a report to the NASA ÂUniversity Design CompetitionÊ. #22 352 Aircraft Design Projects • Diagrams are often a much clearer way of describing complex issues to the audience than text but you will still need to explain the slide carefully. For aircraft design. — #26 356 Aircraft Design Projects aircraft. This is not just a collection of parts of each of the specialist reports but a separate, self-contained and complete description of the aircraft.