The source introduces four key identification concepts, all of which are terms of art in aviation maintenance. The first is the part number (P/N), which designates a specific design standard of a component. Here, part numbers follow the MD Helicopters format: 369 indicates the model series, D indicates a main rotor blade, 21100 or 21600 indicates a drawing number, and the trailing dash number (e.g., -503, -505, -509) indicates a particular modification or variant. The source lists eight distinct P/Ns, some with multiple suffixes separated by a slash (e.g., -503 / -503A / -503M). The slash likely means the list covers all those suffix variants collectively. The second concept is the serial number (S/N), a unique identifier assigned by the manufacturer to each individual blade. The source enumerates hundreds of serial numbers, some purely numeric, others alphanumeric (e.g., “M1858”, “A431”, “B004”, “D539”). The prefix “M” probably denotes a military or special marking; “A”, “B”, “D” may indicate a batch or customer code. The third concept is the dash suffix on serial numbers. For example, under P/N 369D21100-509, the serial number “5120M” appears; under -513, “A549” appears. The “M” suffix on a serial number (as distinct from the “M” on a part number suffix) likely indicates a blade that has been overhauled or modified to a later configuration. The fourth concept is the structural representation of the list. The source uses three formatting methods: simple inline lists separated by spaces; comma-separated inline lists; and a full HTML table with rows, columns, and spacing adjustments to align numbers for readability. The HTML table for P/N 369D21100-509 spans eight columns and four rows, with some cells containing multiple numbers separated by spaces. The table uses precise letter-spacing and line-height values, suggesting it was originally produced for a printed document where alignment matters. No textual explanation accompanies the table. The source does not define any of these concepts. It assumes the reader is familiar with aircraft parts identification, maintenance record keeping, and airworthiness directive structure. There is no mention of “required action”, “compliance time”, “alert service bulletin”, “mandatory replacement”, or “life limit”. The absence of these terms is itself a significant concept: the list is a passive inventory, not an active mandate. The source’s primary conceptual contribution is to establish a precise, verifiable population of affected blades. Each serial number is an entity that can be physically inspected, tracked, and traced through maintenance logs. The list is exhaustive for the given part numbers within the declared serial number range, but it does not say whether later letters or numbers (e.g., beyond Y845 or D549) are excluded or simply not yet known at the time of compilation. The concept of “affected” versus “unaffected” blades is central, but the source does not draw that line explicitly - it only lists what is included.

The source affects four groups of persons and entities, though none is named. The first group are owners and operators of MD Helicopters Model 369 aircraft that have main rotor blades whose part number and serial number match an entry in this list. For those owners, the list may trigger inspection, replacement, or other compliance actions once linked to the underlying airworthiness directive. The second group are maintenance organisations and licensed aircraft maintenance engineers (LAME) who perform work on those blades. They must use this list to determine whether a particular blade in their shop or on the aircraft is subject to the directive. The third group are component suppliers and salvage yards holding stock of these blade part numbers. They would need to check serial numbers before selling or installing a blade, because the directive could prohibit installation of a listed blade unless it has been modified or inspected. The fourth group is regulators, specifically the Civil Aviation Safety Authority (CASA) and any delegated airworthiness bodies that ensure compliance. The list gives regulators a definitive set of blades to monitor. The source does not address who is responsible for cross-checking serial numbers, who bears the cost of the required action, who is liable if a blade is missed, or whether the list applies retrospectively or only to future installations. Notably, the source does not identify any specific persons, companies, or jurisdictions. The part numbers reference MD Helicopters (formerly McDonnell Douglas Helicopter Systems), but the source does not name that company as an affected party. Boeing, which acquired MD Helicopters in 1999, is likewise absent. The list includes serial numbers that suggest worldwide distribution (e.g., “M” prefix for military, various alpha prefixes), so the effect is likely global, but the source gives no territorial limitation. In Australia, the Civil Aviation Act 1988 s 28A and Civil Aviation Safety Regulations 1998 Part 39 govern airworthiness directives, and this list would be incorporated by reference into an AD issued by CASA. However, the source itself does not state that it is an Australian instrument. The presence of document numbers like “20-2380” and “20Z406” could be internal MD Helicopters document numbers, not CASA AD numbers. Therefore, the effect on Australian parties depends on whether CASA has separately adopted this list. The source also includes serial numbers that are duplicated across different part number entries (e.g., S/N 5303 appears under both -501 and -505 lists), meaning a single blade could be subject to multiple requirements if its part number has been re-identified. This creates a compliance trap for anyone who checks only one part number line.

The source imposes no duties and confers no rights. It is a factual list of identifiers. A duty would arise only if a separate instrument (an airworthiness directive or a manufacturer’s alert service bulletin) uses this list to define the scope of an actionable requirement. For example, a typical AD might say: “Within 50 flight hours, remove from service each main rotor blade listed in Appendix A of this AD.” The list itself does not say that. The source does not mention “must”, “shall”, “required”, “prohibited”, “approval”, “exception”, “alternative method of compliance”, “record keeping”, “reporting”, “repetitive inspection”, “life limit”, or “return to service”. Without such language, the list creates no legal obligation. The only “right” that could flow from this list is the right of an owner or operator to know whether a specific blade is included in a mandatory action, and thus whether they must comply. But that is a right by implication, not one the source grants. In Australian law, the right to rely on an airworthiness directive is statutory under the Civil Aviation Act, but the source here is not the directive itself. The source also does not provide any defence or exception. If a blade is not on this list, a person might assume it is not subject to the directive, but the source does not say that blades not listed are safe or approved for continued use. The absence from the list could simply mean the serial number was not yet known when the list was compiled. The source also does not say whether the list is exclusive (i.e., only these serial numbers are affected) or illustrative (i.e., other serial numbers may also be affected). The use of ranges and individual numbers suggests an attempt at completeness, but the lack of language like “including but not limited to” or “the following” leaves ambiguity. A duty could also arise under the general duty clause of the Civil Aviation Act (s 29B: duty to maintain aircraft in airworthy condition), but again that duty exists independently of this list. The source therefore cannot be used as a standalone compliance document. Anyone claiming a right to resist an enforcement action because a blade is not on the list would need to check the full AD. Conversely, an operator could not be penalised for failing to comply with a duty that exists only in this list, because the list does not state the duty. In summary, this source creates no enforceable duties or rights. It is a passive reference schedule.

The source contains no penalty provisions, no enforcement mechanisms, no maximum fines, no imprisonment terms, no infringement notice amounts, no default rules, and no delegation of enforcement powers. It is impossible to derive any penal consequence from this document alone. Under the Australian civil aviation regulatory regime, penalties for non-compliance with an airworthiness directive arise under the Civil Aviation Act 1988 (e.g., s 29A - contravention of a condition of an airworthiness certificate; s 32 - penalties for operating an unairworthy aircraft) and the Civil Aviation Safety Regulations 1998 (e.g., reg 39.020 - failure to comply with a direction). A typical AD will specify a compliance time and state that failure to comply is an offence attracting a penalty of up to 200 penalty units for an individual and 1,000 penalty units for a corporation (currently about $44,000 and $222,000 respectively). But none of that language is in this source. The source also says nothing about who enforces the list: no reference to CASA, the Australian Transport Safety Bureau (ATSB), state police, or the Director of Public Prosecutions. It does not mention powers of search, seizure, or grounding. It does not create a right of review or appeal. The only enforcement inference one could draw is that the list is part of a broader safety regulation system, but that inference comes from external knowledge, not from the source itself. If a blade listed here fails without a compliance record, an operator might face enforcement action. But the source itself is neutral. It does not even say “mandatory”. The word “mandatory” does not appear. Therefore, from the source alone, there are zero penalties or enforcement provisions. A competent practitioner would treat this list as, at most, evidence of what is covered by a separate direction. The absence of penalties also means the source cannot be used to ground a private right of action for negligence or breach of statutory duty. A plaintiff would need to point to the operative AD, not this schedule. In terms of enforcement risk, the only real risk is that someone fails to check this list and later discovers that a blade they installed was subject to an unreleased AD. But that risk is not created by the list; it is created by the underlying obligation to keep current with airworthiness information. The source does not even provide a date of issue, so one cannot know if it is still current or superseded.

The source does not reference any other statute, regulation, or common law principle. It cites no act number, no regulation name, no standard (e.g., ASTM, ISO, EASA, FAA). It does not mention the Civil Aviation Act 1988, the Civil Aviation Safety Regulations 1998, the Air Navigation Act 1920, the Transport Safety Investigation Act 2003, the Work Health and Safety Act 2011, or any overseas legislation such as the US Federal Aviation Regulations (14 CFR). It does not refer to the Australian Consumer Law, the Competition and Consumer Act 2010, the Criminal Code Act 1995 (in relation to strict liability), or the Evidence Act 1995 (in relation to documentary evidence). It does not interact with any contract law doctrine (e.g., implied terms, breach of warranty, or force majeure) because it does not state any contractual effect. It does not modify any common law duty of care in tort. The only interaction one can infer is that this list would typically be incorporated by reference into an airworthiness directive, which in turn operates under Part 39 of CASR 1998. Under CASR 39.005, an AD may adopt a manufacturer’s list by reference. If CASA has done that, then this list becomes legally enforceable. But the source does not confirm that. The source also does not say whether it supersedes any previous lists. Without a repeal or amendment clause, it is impossible to know how this list relates to earlier or later lists. It may conflict with other documents that list different serial numbers for the same part number (e.g., a service bulletin that says all blades P/N 369D21100-505 are affected regardless of serial number). The source does not address that. Furthermore, the source does not interact with the law of evidence: it is a schedule, and its admissibility in court to prove that a specific blade is subject to a mandatory action would depend on whether it is incorporated in an AD and whether the AD is admissible. The source itself has no legislative status; it is likely an extract from a manufacturer’s document. In Australian law, extrinsic materials like this have limited evidentiary weight unless properly authenticated. The source also does not interact with the Privacy Act 1988 (it contains no personal information), the Freedom of Information Act 1982 (it is presumably a published document), or the Archives Act 1983. It might interact with the law of intellectual property if it is a copyright work, but the source does not assert any copyright claim. In summary, this source stands alone and gives no indication of its place in the hierarchy of legal instruments. Its legal effect is zero until it is linked to an operative provision in another instrument.

The source contains no amendment history. There is no list of previous versions, no effective dates, no sunset dates, no review dates. The only date-like references are “1991” and “20-2380”, which appear at the top of the document. “1991” is likely the year the document was generated, but the document could have been revised since then. The source includes various part number suffixes such as -503A and -503M, which may indicate that the list was amended to include new variants after the original -503 list was published. The serial number ranges also show a mix of low and high numbers (e.g., 0145 to 8684 for P/N 369D21100-509), which could mean the list was updated multiple times as new blades entered service. However, the source does not flag which serial numbers were added at what date. It does not use footnotes, strike-throughs, revision bars, or version numbers. The lack of an amendment history makes it impossible to determine whether this list is current. A prudent maintenance organisation would need to cross-reference this list against the latest AD from CASA or the FAA to see if it has been superseded. The source also does not indicate whether any serial numbers have been removed (e.g., due to earlier replacement or correction of misidentified numbers). The HTML table formatting for the -509 list uses precise spacing that might reflect a specific point in time when the list was finalised. Without a revision date, the user cannot know if the list is still operative. In Australian regulatory practice, airworthiness directives are given AD numbers (e.g., AD/369/75) and are updated by amendment notices. This source has none of that. Therefore, from this source alone, the amendment history is blank. Anyone relying on this list must assume it is a snapshot, not an authoritative current listing. The safest course is to treat it as historical and verify against the latest regulatory database.

The source contains no references to any court cases, tribunal decisions, administrative appeals, or enforcement proceedings. It does not cite any verdicts, settlements, or judgments. It does not mention Coronial inquests, ATSB reports, or civil litigation related to blade failures or airworthiness directive compliance. There are no case names, citation numbers, or legal principles discussed. The absence of litigation history is not surprising given the source is a technical parts list. However, for a legal deep dive, it is significant that the source provides no guidance on how courts have interpreted similar lists or what the standard of proof is for establishing that a blade was covered. In Australian law, there have been cases concerning the enforceability of airworthiness directives (e.g., Australian Air League v CASA, R v Mackay), but this source does not mention or adopt any reasoning from those cases. The source also does not address any class actions or product liability claims related to MD 369 rotor blades. The lack of litigation history means the source is legally inert from a precedent perspective. It does not create any principle of law. It does not limit or expand any common law doctrine. It could be used as evidence in a future case, but its probative value would depend on authentication and relevance. In summary, there is no litigation history to report from this source; the source itself is not a court document.

Several traps lie hidden in this source. First, the list of serial numbers under each part number appears exhaustive but is not guaranteed to be complete. The source does not say “only the following” or “including but not limited to”. A maintenance organisation that checks a blade against this list and finds no match might wrongly assume the blade is exempt, when in fact the directive may cover all blades of that P/N regardless of serial number, or the directive may have been amended to include additional serial numbers after this list was printed. Second, the same serial number appears under multiple part numbers. For example, S/N 5303 appears under P/N 369D21100-501 and also under P/N 369D21100-505. This could happen if a blade was originally built as a -501 and later re-identified as a -505 after a modification. A person checking only one P/N line might miss that the blade is also listed under a different P/N. Third, the use of dash suffixes (e.g., -503, -503A, -503M) grouped together under one heading is ambiguous. It is unclear whether the list applies to all three variants collectively or only to the basic -503 version. The slash (“/”) might indicate “including”. A literal reading would include all serial numbers under that heading for all three suffixes. But if -503A blades have different design features, they might need separate inspection criteria. Fourth, the source contains serial numbers that are not strictly numeric. For example, “M1858”, “A431”, “B004”, “D549”. An alphabetical prefix could indicate a special marking, a military contract, or a post-overhaul re-identification. A technician used to numeric-only lists might overlook these alphanumeric entries. Fifth, the source includes serial numbers that are written with leading zeros (e.g., 0073, 0321, 0145). A database or spreadsheet might strip leading zeros, causing a mismatch when checking. Sixth, the HTML table for P/N 369D21100-509 uses non-standard spacing. If the source is printed or rendered differently, numbers could be misaligned, leading to misreading. Seventh, the source does not include the suffix “-513M” for the last entry (369D21613-11). The list is truncated; it shows only the part number header and no serial numbers. That is incomplete. Anyone relying on this source for that part number would have no information. Eighth, the source does not state whether the list is mandatory or advisory. A non-expert might assume it is mandatory (because it looks official) and take unnecessary action, or assume it is merely informative and skip necessary action. Ninth, the source uses two different formats for the -509 list: an inline list for some variants and an HTML table for others. The table includes cells that appear empty or have only one number, which could be confused with missing data. Tenth, there is no reference to a compliance time. If a blade is on this list, the required action might be immediate or within 100 hours, but the operator cannot tell from this source. Eleventh, the source includes a document number “20-2380” and “20Z406”, which could be internal MD Helicopters document numbers, not CASA AD numbers. An Australian operator might search CASA’s AD database and not find this exact number, leading to confusion about its regulatory status. Twelfth, the source does not include any contact information for questions or for reporting non-compliance. Thirteenth, the source appears to be extracted from a larger document; the first line “1991 20-2380 20Z406 2217 2218 29B075 49B936 7888 7964 88-7008 AC10 AD59 AD68 AD74 AD98 AE55 AF47 AF57 AG66 AH28 AH82 AH92 AJ72 AK49 AL07 AL12 AL34 AL41 AL49 AM10 BC84 BC86 DC97 N579 N701 T667 U537 U762 V129 V297 V305 W314 W705 Y249 WW784 Y268 Y607 Y608 Y641 Y653 Y666 Y681 Y734 Y845.” is itself a string of numbers and letters that may represent document control numbers, drawing numbers, or other batch identifiers. It is not explained. A reader might misinterpret that string as part of the mandatory text. In short, the source is dense with opportunities for misapplication. Professional caution is essential.

Compliance cannot be determined from this source alone, because the source does not state what action is required. To comply, a person who encounters this list must take the following steps. First, identify the originating regulatory instrument. Look for an airworthiness directive from CASA (or the FAA if operating under US approval) that references MD Helicopters Model 369 rotor blades P/N 369A1100-503 series, 369D21100 series, or 369D21600 series. The AD number may be AD/369/75 or similar. Check the AD’s applicability section: if it says “serial numbers listed in Appendix A”, then this list is that appendix. If the AD says “serial numbers listed in MD Helicopters Service Bulletin SB369-XX”, then this list may be an extract from that bulletin. Without the AD, compliance is impossible. Second, verify the effective date of the AD. ADs often have a compliance time commencing from the date of issue. This list has no date, so the operator must use the AD’s date. Third, physically locate every main rotor blade on the aircraft or in the spares inventory that matches the part numbers in this list. Record the serial number of each blade. Fourth, compare each serial number against the lists. If the serial number appears, the blade is subject to the AD. If it does not appear, it may still be subject if the AD says “all serial numbers” or if the list is not exhaustive. Assume the worst: treat a missing serial number as potentially covered until confirmed otherwise. Fifth, perform the required action stated in the AD. Typical actions for rotor blade ADs include: inspect for cracks using eddy current or dye penetrant; replace if cracks found; lifetime limit (remove at a certain number of flight hours); or rework/replace to a later standard. This source give no clue, so the operator must find the AD text. Sixth, document compliance in the aircraft maintenance log and the component history card. Record the serial number, the part number, the AD number, the compliance method, and the date. Seventh, if the AD permits alternative methods of compliance (AMOC), apply to CASA for approval before deviating. Eighth, check for supersession: a later AD may have replaced this list. Search CASA’s AD database for any later AD addressing the same blades. Ninth, if this list is from a foreign authority (e.g., FAA AD 91-2380), determine whether CASA has adopted it via a separate AD or by reference under a bilateral agreement. In Australia, foreign ADs are not automatically binding; they must be implemented by CASA. Tenth, train maintenance staff to recognise this list format: do not ignore the HTML table or the alphanumeric serial numbers. Create a controlled copy of the list and update it whenever the AD is revised. In summary, compliance is a multi-step process that begins with finding the missing operative instrument. This source is the starting point, not the end. Without the underlying AD, any attempt to comply is guesswork. A record of having checked the list and found no match should be kept, but it does not guarantee the blade is compliant - only that it is not on this particular snapshot. The safest compliance strategy is to treat any MD 369 rotor blade with the listed part numbers as potentially affected, regardless of serial number, until the full AD is consulted.