31oct12

2012/13
Rules and Vehicle Design
Initial Rules Posting: 18 Aug 2012
Latest Update: 31 oct 12
Entry Deadline: 31 Oct 2012
The contest rules may be augmented/supplemented at any time during the
competition
through the Q&A process.
Summary:
The AIAA through the Applied Aerodynamics, Aircraft Design, Design Engineering and Flight Test Technical Committees and the AIAA Foundation invites all university students to participate in the Cessna Aircraft Company/Raytheon Missile Systems - Student Design/Build/Fly Competition. The contest will provide a real-world aircraft design experience for engineering students by giving them the opportunity to validate their analytic studies.
Student teams will design, fabricate, and demonstrate the flight capabilities of an unmanned, electric powered, radio controlled aircraft that can best meet the specified mission profile. The goal is a balanced design possessing good demonstrated flight handling qualities and practical and affordable manufacturing requirements while providing a high vehicle performance.
To encourage innovation and maintain a fresh design challenge for each new year, the design requirements and performance objectives will be updated for each new contest year. The changes will provide new design requirements and opportunities, while allowing for application of technology developed by the teams from prior years.
Check the rules package carefully as items and approaches that were legal in past years may not be legal for this contest year. Only the contents of this Rules package, the 2013 FAQ, and 2013 Q&A documents hold bearing on the requirements and/or allowances for the current contest year. It is the responsibility of the teams to know and follow all provided rules, the FAQ, and all contest day briefings.
Cash prizes are $2500 for 1st, $1500 for 2nd and $1000 for 3rd place. The winning team will be invited to present their design at an AIAA conference. The team with the best Report Score will receive a $100 prize from the Design Engineering Technical Committee.
Judging:
Students must design, document, fabricate, and demonstrate the aircraft they determine to be capable of achieving the highest score on the specified mission profile(s). Flight scores will be based on the demonstrated mission performance obtained during the contest.
Each team must also submit a written Design Report. A maximum of 100 points will be awarded for the team design report. The overall team score is a combination of the Design Report score, Flight score and Rated Aircraft Cost (RAC). The team with the highest overall team score will be declared the winner. Scores will be FINAL 7 working days after the completion of the contest. This period will allow for review of the scores in a timely fashion following the contest.
All submitted reports are the property of AIAA, Cessna and Raytheon and may be published or reproduced at their discretion.
Contest Site:
Host for the competition will be Raytheon Missile Systems. The fly-off is planned to be held at the TIMPA field in Tucson, AZ. Details on the contest site and schedule will be sent to registered teams early in the fly-off calendar year. You can check on historical weather conditions at www.weatherbase.com or www.weatherunderground.com.
Teams are advised to check with their airlines on what materials they will be allowed to bring both to and from the contest site. Hazmat items like paints, thinners and glues may need to be purchased locally and PROPERLY disposed of following the contest.
Team Requirements:
All team members (except for a non-student pilot) must be full time students at an accredited University or College and student members of the AIAA. At least 1/3 of the team members must consist of Freshman, Sophomores or Juniors. The pilot must be an AMA (Academy of Model Aeronautics) member. Teams may use a non-university member for the pilot if desired. We will provide qualified pilots at the contest on an as-available basis to assist teams who are unable to have their pilot attend.
Team members may be updated/changed at any time during the contest but must always comply with the 1/3 rule. Following the initial team postings at the contest beginning we will make a “One Time” update to the team member lists posted on the website. Teams wishing a team member list update must submit an updated copy of the contest entry form with all fields fully filled (but only the team member information may be changed). We will notify teams when the website update change information may be sent, normally in February.
Each educational institution may submit one (1) team entry. The team members may be changed during the contest period, so schools may use an internal selection process to determine their final design and team members prior to the written report submission and fly-off. For schools with multiple campuses in different cities each campus will be considered as a separate entity.
Two or more schools may combine to submit a single entry.
Schools which already have an entry may not have additional students from their school participate as members of a team from a different (shadow) school.
The number of entries is limited to a maximum of 100 teams. If more than the maximum number of team entries is received during the submission period a random selection will be used by the judges to down-select to the final team list.
Past Year Reports:
Winning team design reports from prior contest years are posted on the contest website as examples. Note that the formatting and content has evolved from one year to the next. Only the rules noted in this document apply for the current year. The top scoring report(s) from this year’s contest will be placed on the contest web site for the next year’s competition.
Sponsorship:
Teams may solicit and accept sponsorship in the form of funds or materials and components from commercial organizations. All design, analysis and fabrication of the contest entry is the sole responsibility of the student team members.
Schedule:
A completed electronic entry must be RECEIVED by 5 PM US East Coast Time on 31 October 2012. Entry forms may not be submitted before 15 October.
The DBF entry form is different from the ones used for other AIAA student competitions. The DBF entry form can be found on the contest web site. It must be submitted by e-mail to the contest administrator at director@aiaadbf.org .
Be sure to include ALL information requested in the form. We will use the first (valid) entry received so be sure all supplied information is correct the first time..
Incomplete entry forms will not be accepted. Incomplete forms will be returned for correction and may miss the deadline
It is the teams responsibility to make sure the e-mail contact addresses they supply remain active during the entire period from entry to the close of the competition, as e-mail will be the primary means to provide information and updates. Do not use an internal team correspondence e-mail list server as your point of contact e-mail address.
Note: The AIAA mail servers will not send e-mail to @hotmail.com addresses. Do NOT use a hotmail address for any of your team contacts or e-mail.
Design reports must ARRIVE at the designbuildfly@gmail.com email by 5 pm US East coast time on 25 February 2013.
Reports will be judged “as received”, no corrections/additions/changes will be made by the organizers so check your reports carefully before sending them.
Teams may only submit one report copy, any copies received after the initial submission will be deleted.
Submission of reports electronically only (no hard copy required) is new this year. The details for the electronic report format and submission are at the end of the report section in this rules document.
The contest is scheduled for 19-21 April 2013. The competition is anticipated to run from 8AM to 7PM on Friday, 7AM to 7PM on Saturday and 7AM to 6PM Sunday. Awards will be presented at 5:30PM on Sunday. All teams should plan their travel so that they may stay for the awards presentations on Sunday. A final contest schedule will be e-mailed to the teams prior to the contest date.
Tech inspections will begin on Friday and will continue as required on Saturday and Sunday.
To help streamline the contest flow and maximize opportunities for each team to get their flights in the Tech inspections will be conducted in the same order as the flight rotation (which is based on report scores) so that the first teams inspected will be the first teams in the flight queue. Teams may use the sequence to help estimate when they need to arrive at the contest site to make sure they do not miss their slot in the first tech inspection rotation.
|
Note: All schedule deadlines are strictly enforced. Late entries will NOT be accepted. Late report submissions will NOT be judged. Teams who do not submit the required electronic report will NOT be allowed to fly. It is the team’s responsibility to assure that all deadlines are known, understood and met. |
Communications:
The contest administration will maintain a World Wide Web site containing the latest information regarding the contest schedules, rules, and participating teams. The contest web site is located at:
http://www.aiaadbf.org
Questions regarding the contest, schedules, or rules interpretation may be sent to the contest administrator by e-mail at:
director@aiaadbf.org
Questions received prior to the official entry submission date will not be answered directly. Select questions “may” be answered in the FAQ prior to the entry submission date. Official questions and answers received following the entry submission date will be posted on the website.
This year, the DBF Organizing Committee will utilize Facebook as an additional means of communicating with the teams during the contest weekend only. This will NOT be a means of communicating rules, FAQ's, protests, etc, but only used in case of emergencies, weather delays or contest weekend schedule updates. Additional information will be included in a contest site/ schedule email to be sent out to the registered teams prior to the fly-off..
Aircraft Requirements - General
The aircraft may be of any configuration except rotary wing or lighter-than-air.
No structure/components may be dropped from the aircraft during flight.
No form of externally assisted take-off is allowed. All energy for take-off must come from the on-board propulsion battery pack(s).
Must be propeller driven and electric powered with an unmodified over-the-counter model electric motor. May use multiple motors and/or propellers. May be direct drive or with gear or belt reduction.
Motors may be any commercial brush or brushless electric motor.
For safety, each aircraft will use a commercially produced propeller/blades. Must use a commercially available propeller hub/pitch mechanism. Teams may modify the propeller diameter by clipping the tip and may paint the blades to balance the propeller. No other modifications to the propeller are allowed. Commercial ducted fan units are allowed.
You can change the propeller diameter/pitch for each flight attempt.
Motors and batteries will be limited in current draw by means of a 20 Amp fuse in the line from the positive battery terminal to the motor controller.
Fuse(s) must be located such that no propulsion system component: motor; motor controller; or battery may see more current than the stated limit (fuse value).
Only ATO or blade style plastic fuses may be used.
Must use over the counter NiCad or NiMH batteries. For safety, battery packs must have shrink-wrap or other protection over all electrical contact points. The individual cells must be commercially available and the manufacturers label must be readable/documented (i.e. clear shrink wrap preferred). All battery disconnects must be "fully insulated" style connectors.
Maximum propulsion battery pack weight is defined in the mission rules section. This battery pack must power propulsion systems only. Radio Rx and servos MUST be on a separate battery pack. Batteries may not be changed or charged between sorties during a flight period.
Aircraft and pilot must be AMA legal. This means that the aircraft TOGW (take-off gross weight with payload) must be less than 55-lb, and the pilot must be a member of the AMA.
Since this is an AMA sanctioned event, the team must submit proof that the aircraft has been flown prior to the contest date (in flight photo) to the technical inspection team. We will provide qualified pilots at the contest on an as-available basis to assist teams who are unable to have their pilot attend.
The aircraft must remain substantially the same as documented in the report (for example you can not change a flying wing design to a conventional tail design). You may make small modifications to the design to improve flight performance after the report submission (one example would be changing a control surface size).
Aircraft Requirements - Safety
All vehicles will undergo a safety inspection by a designated contest safety inspector prior to being allowed to make any competition flight. All decisions of the safety inspector are final.
To speed the tech inspection process each team must present a signed Pre-Tech and First-Flight Certification when called to begin their on-site tech inspection. Teams may not begin the on-site tech inspection without a completed certification. The Pre-Tech and First-Flight Certification sheet is available on the contest website.
The Pre-Tech must be conducted by, and signed off by, a non team member RC pilot or the team faculty advisor. The Pre-Tech will cover the same safety of flight requirements as the on-site tech inspection and will assist teams in making sure they are ready and able to pass the on-site tech inspection the first time. An expanded First-Flight requirement, which also must be signed off by a non team member RC pilot or the team faculty advisor, requires demonstration of a complete flight including take-off, flying a minimum flight pattern, and landing in a pre-designated location without damage to the aircraft. The non team member RC pilot who signs the inspection and flight certifications may be the same as a team's non-student contest pilot.
Safety inspections will include the following as a minimum:
Throttle closed
Full up elevator
Full right rudder
Full right aileron
Full Flaps down (if so equipped)
The radio Fail Safe provisions will be strictly enforced.
Scoring:
In the event that, due to time or facility limitations, it is not possible to allow all teams to have the maximum number of flight attempts, the contest committee reserves the right to ration and/or schedule flights. The exact determination of how to ration flights will be made on the contest day based on the number of entries, weather, and field conditions. In the event of a tie, Report Score will take precedence over Flight Score as a tie-breaker.
Each team's overall score will be computed from their Written Report Score, Total Flight Score and Rated Aircraft Cost using the formula:
SCORE = Written Report Score * Total Flight Score / RAC
The total flight score is the sum of the individual mission flight scores: Total Flight Score = M1 + M2 + M3
The RAC is a function of empty weight and size factor. RAC = Sqrt(EW * SF) / 10
Empty weight will be measured after each successful scoring flight: EW = Max(EW1, EW2, EW3)
EWn is the post flight weight with the payload removed
Size factor, SF = X_max + 2* Y_max
SF measurements will be made with the aircraft in it's full flight configuration.
X_max is the longest possible dimension in the direction of flight.
Y_max is the longest possible dimension perpendicular to the direction of flight.
Measurements will be made "point-to-point" on the aircraft so may not necessarily be parallel to the ground or the the aircraft flight axis.
Point-to-Point measurements will curve around portions of the aircraft as needed.
The measurement path with the shortest length, going either "over" or "under" the aircraft, will be used.
If the wing tip trailing edge or the horizontal tail trailing edge is aft of the fuselage aft point then teams must bring a board with them that spans the wing/horizontal tip trailing edges to create a measurement reference.
Mission Task Matrix:
Joint Strike Fighter
General:
Battery pack(s) maximum weight limit is 1.5 lb.
Teams will be allowed a maximum of 4 flight attempts or 3 successful scoring flights. Once a mission has a successful scoring flight it may NOT be repeated to try to improve the score.
All payloads must be secured sufficiently to assure safe flight without possible variation of aircraft cg during flight.
Assembly/flight line crew is limited to pilot, observer and 1 ground crew.
Scoring measurement units are feet; lbs,; and seconds.
Mission Sequence:
- Missions must be flown in order. A new mission can not be flown until the team has obtained a successful score for the preceding mission.
- Aircraft must be designed to be capable of performing all required missions.
Specifically this requires that teams must show that all payloads fit in the aircraft during the tech inspection.
- Teams will be asked to load configuration #1 (of mission #3) and must present photographs showing configurations #2-6 installed.
- Aircraft must pass the wing tip load test with the larger of 4 internal stores or the maximum number of internal stores the team will attempt to fly for mission #2 plus one store "Der Red Max" on each inboard wing pylon
- The number of internal stores demonstrated will be recorded and can not be altered after completing tech inspection.
- The aircraft will enter the assembly area with the payload for mission 2 and 3 uninstalled.
- The team will have a total of 5 minutes to load the payload and checkout the aircraft systems as fully functional.
- There is no work allowed on the aircraft after the loading/checkout time.
- The RC receiver should be able to be turned on externally or must be left on. You will not be allowed to re-open any compartment after the loading/checkout time to turn on the receiver.
- Only the assembly crew member, pilot and pilot assistant may go to and enter the staging box.
- After the checkout is complete the assembly crew member may be swapped for a different flight line crew member if desired.
- The initial upwind turn on the first lap of each mission will occur after passing the turn judge (signaled by raising a flag). The aircraft must remain in unaided visual control distance of the pilot at all times. The Flight Line Judge may require turns to be made to remain in a safe visual control range at his discretion.
Missions:
Aircraft will use ground rolling take-off and landing
Missions will simulate take-off from a small austere field.
The aircraft will be placed such that all ground contact points are completely inside an approximately 30 x 30 ft square marked on the runway.
Aircraft must successfully take-off before crossing any edge of the square.
Aircraft must complete a successful landing at the end of each mission for the mission to receive a score.
A successful landing is outlined in the general mission specification section below.
Mission 1 - Short Take-off
- Take-off within the prescribed area.
- Maximum number of complete laps within a 4 minute flight time
- Time starts when the throttle is advanced for the (first) take-off (or attempt)
- A lap is complete when the aircraft passes over the start/finish line in the air
- Mission performance will be normalized over all teams successfully completing this mission.
- Mission score M1= 2 * (N_Laps_Flown/Max_N_Laps_Flown)
- Must complete a successful landing to get a score
- Mission 2 - Stealth Mission
- Take-off within the prescribed area.
- 3 Lap internal-stores flight.
- Stores must be carried internal to the aircraft in the main fuselage (not a secondary pod) or completely inside the wing.
- Access to the stores for loading must be through the lower surface of the aircraft, representative of bay doors though the doors need not be mechanized.
- Stores must be aligned to the direction of flight (tails aft, body along flight axis).
- Internal stores must be secured to a mounting structure/rack that is a permanent part of the aircraft structure.
- They must be secured and positioned such that they "could" be released "down" one at a time.
- Stores must not contact each other or any part of the aircraft structure except for the specified mount/rack.
- Store mounting points must secure the store by/on the store body.
- Stores do not need to be capable of remote release (stores will not be released as part of the flight).
- No special fairings or blisters may be added to the aircraft, all external surfaces must be the same for all 3 missions.
- Weight of internal fixtures used to secure stores WILL be included in the Empty_Weight measurement.
- Mission performance will be normalized over all teams successfully completing this mission.
- Mission score M2= 4 * (N_Store_Flown/Max_N_Store_Flown)
- Must complete a successful landing to get a score
Stores Configuration:
Internal Mini-Max Number determined by team
- May not be zero and may not exceed number demonstrated in tech inspection- Mission 3 - Strike Mission
- Take-off within the prescribed area.
- 3 lap mixed-stores flight.
- Payload will be a random draw of internal and external stores (Roll of 1 dice).
- Teams will roll the dice when entering the assembly area.
- Internal stores must follow requirements outlined for Mission 2
- External stores must be wing pylon mounted and fully external to the wing profile (no submerged stores).
- Store fins must be below the wing lower surface trailing edge height.
- Store mounting points must secure the store by/on the store body
- Weight of removable pylons WILL NOT be included in the Empty_Weight (EW3) measurement
- External stores may not overlap/block the access/deployment area of internal store location(s).
- Stores must have a minimum store-to-store separation of 3" on centerline.
- The most inboard store(s) centerline must be at least 3" from the aircraft centerline.
- Mission performance will be normalized over all teams successfully completing this mission.
- Mission score M3= 6 * (Fastest_Time_Flown/Team_Time_Flown)
- Time starts when the throttle is advanced for the (first) take-off (or attempt)
- Time ends when the aircraft passes over the finish line (in the air) at the completion of the last lap.
- Must complete a successful landing to get a score
Stores Configurations: (corrected load-out)
Payload Configuration
(roll dice)1 2 3 4 5 6 Internal Mini-Max 4 - 2 - - 1 Left Wing Mini Honest john - - - 2 - - High Flyer - 1 - - 1 1 Der Red Max 1 1 1 - 1 1 Right Wing Mini Honest john - - 2 2 2 1 High Flyer - 1 - - - 1 Der Red Max 1 1 - - - -
Stores:
- Each team will provide a case containing the stores inventory defined below, including the required removable pylon assemblies.
- Stores case must have a latching lid and be able to be opened on one side only (no collapsing cases)
- Store mounts (pylons) are not part of store weight.
- External pylons will be removed for empty weight (EW) measurements.
- Internal store mounting provisions will be included in EW measurement..
- Store minimum weights will be verified after each successful flight (not during the tech inspection)
- Store may have no additional "features" beyond what is defined in the kit (ie. they must be built exactly to the kit instructions and configuration with the sole exception of adding internal ballast)..
- Required stores inventory: (corrected weights)
- min 4 x Estes p/n 002445 Mini-Max - internal payload - ballast to 0.25 lbs each (minimum)
- 2 x Estes p/n 002178 Hi-Flyer - external payload - ballast to 0.50 lbs each (minimum)
- 4 x Estes p/n 002446 Mini Honest John - external payload - ballast to 0.75 lbs each (minimum)
- 2 x Estes p/n 000651 Der Red Max - external payload - ballast to 1.0 lbs each (minimum)
- Each store must have it's model (name) and the required minimum weight printed on the body exterior.
- For foreign teams, the Estes overseas distributor is:
Logic RC Limited
12-18 Hartham Lane
Hertford, SG14 1QN, United Kingdom
Tel: +44(0) 01992 558226
Email: mail@logicrc.com
Website: www.logicrc.com
Flight Line Order:
A flight order list will be generated and emailed to the teams on the Wednesday prior to the fly-off weekend. Teams will always rotate in this order. The flight order will be repeated continuously.
The flight order list will carry over from Friday to Saturday and Saturday to Sunday at what ever spot in the rotation it leaves off.
Each team’s position in the flight order will be determined from their written report score, highest report score goes first.
Report scores will be available following the pilot briefing at the start of the contest (they will not be included with the rotation sequence e-mail).
There will be four staging box positions near the flight line.
If you are not ready to enter a staging box when your rotation number comes up you will miss your opportunity for that rotation.
Note: Teams will be notified when to enter the staging box. It is each team's responsibility to monitor the notifications from the scoring table in order to respond if ready. A contest official will be available to help teams enter the staging box.Electing to enter one of the staging box positions on your turn in the rotation order will constitute using a flight attempt.
If you choose to leave the staging box for any reason you will forfeit that flight attempt.
If you go to the flight line and are not able to begin your flight when instructed you will forfeit that flight attempt.
General Mission Specification and Notes:
The aircraft propulsion system(s) must be "safed" (fuse removed) during any time when crew members are preparing/handling the aircraft.
Maximum flight support crew is: pilot, observer, and ground crew.
Observer and all ground crew must be students. Only the pilot may be a non-student.
The upwind turn will be made after passing the upwind marker. The downwind turn will be made after passing the downwind marker. Upwind and downwind markers will be 500 ft from the starting line. Aircraft must be "straight and level" when passing the turn marker before initiating a turn.
Aircraft must land on the paved portion of the runway. Aircraft may "run-off" the runway during roll-out. Aircraft may not “bounce” off the runway.
Aircraft obtaining “significant” damage during landing will not receive a score for that flight. Determination of “significant” is solely at the discretion of the Flight Line Judge.
Flight altitude must be sufficient for safe terrain clearance and low enough to maintain good visual contact with the aircraft. Decisions on safe flight altitude will be at the discretion of the Flight Line Judge and all rulings will be final.
Additional information is included in the FAQ (Frequently Asked Questions).
Flight Course:
The orientation (direction) of the flight course will be adjusted based on the prevailing winds as determined by the Flight Line Judge. The flight course will be positioned to maintain the greatest possible safety to personnel and facilities. The nominal flight course is shown in the Figure below.

Protest Procedure:
Submitting a protest is a serious matter and will be treated as such. Teams may submit a protest to the Contest Administration at any time during the competition. Protests may not be submitted after the conclusion of the competition. Protests must be submitted in writing and signed by the team advisor, designees are not allowed for protest submissions. If the team advisor is not present, he may FAX or email a signed protest to the team for them to present. Remotely submitted protests must be on hard copy (printed by the team) and have the advisors signature. A phone number where the advisor may be contacted must be provided.. Protests may be posted for review at the decision of the administration.
Protests and penalties (up to disqualification from the contest for deliberate attempts to misinform officials, violate the contest rules, or safety infractions) will be decided by the Contest Administration. Protests submitted but not upheld by the judges may be given a penalty of the loss of one flight score to the team submitting the protest. The decision of the Contest Administration is final.
Design Report:
Each team will submit a judged design report as outlined below and in the SCHEDULE section above.
|
Note: Reports must strictly adhere to the following requirements. Failure to meet requirements will result in penalties that range from score reduction to elimination from the contest.
|
Reports will be scored on a 100 point basis following the guidelines outlined below.
All information used for scoring must be in the outlined sections, content that is out of sequence, including the drawing package, will be treated as missing and scored accordingly.All reports must be one and one half line spacing, 10-pt Arial font. Tables and figures should be clear and readable for the judges. The reports will be judged on format and readability.
ALL items requested below should be present, easy to locate and identify, well documented and in the correct section for full scoring.
Examples of winning team design reports from prior contest years are posted on the contest website. Note that the formatting and content has changed from one year to the next. Prior year reports may not reflect or meet the rules listed for the current year.
Design Report
All section scores will include format, completeness and readability
1. Executive Summary: (10 points):
· Provide a summary description of your selected design and why it is the best solution to the specified mission requirements.
· Describe your key mission requirements and design features keyed to those requirements.
· Document the performance/capabilities of your system solution.
2. Management Summary (5 points):
· Describe the organization of the design team.
· Provide a chart of design personnel and assignment areas.
· Provide a milestone chart showing planned and actual timing of the design / fabrication / testing processes.
3. Conceptual Design (15 points):
· Describe mission requirements (problem statement).
· Translate mission requirements into design requirements.
· Review solution concepts/configurations considered.
· Describe selection process and results.
4. Preliminary Design (20 points):
· Describe design/analysis methodology
· Document design/sizing trades
· Describe/document mission model (capabilities and uncertainties)
· Provide estimates of the aircraft lift, drag and stability characteristics.
· Provide estimates of the aircraft mission performance.
5. Detail Design (30 points total. 15 points for discussion items, 15 points for drawing package):
· Document dimensional parameters of final design.
· Document structural characteristics/capabilities of final design.
· Document systems and sub-systems design/component selection/integration/architecture.
· Document Weight and Balance for final design. Must include a Weight & Balance table for the empty aircraft and with each of the possible payloads
· Document flight performance parameters for final design.
· Document mission performance for final design.
Drawing Package
· 3-View drawing with dimensions.
· Structural arrangement drawing.
· Systems layout/location drawing.
· Payload(s) accommodation drawing(s).
6. Manufacturing Plan and processes (5 points):
· Document the process selected for manufacture of major components and assemblies of the final design.
· Detail the manufacturing processes investigated and the selection process/results.
· Include a manufacturing milestone chart showing scheduled and actual event timings.
7. Testing Plan (5 points):
· Detail testing objectives, schedules, and check-lists.
8. Performance Results (10 points):
· Describe the demonstrated performance of key subsystems and compare it to predictions from Section 5. Explain any differences and improvements made.
· Describe the demonstrated performance of your complete aircraft solution and compare it to predictions from Section5. Explain any differences and improvements made.
Design Report Electronic Submission
Each team must provide an electronic copy of their final design report for the report judging as outlined below.
Electronic copy must Arrive at the designbuildfly@gmail.com email by 5PM US East Coast time on 25 February 2013.
Electronic report files must be named: “2013DBF_[university].PDF”
Electronic report must be a single file with all figures/drawings included in the proper report sequence in PDF format.
(Free PDF file conversion programs are available on the Internet, such as www.pdf995.com.)Electronic reports should have all figures compressed to print resolution to minimize file size.
Electronic reports must be less than 20 MB in size (including encoding for e-mail transmission).
Reports not following the name format or exceeding the file size will be rejected. We will notify the team "if" the reports do show up in the email 'in' box. If reports are rejected by the email system for being too large we will NOT be able to send a notification of the problem to the team!
[AIAA Student Design/Build/Fly Competition homepage] [AIAA Homepage]