BRP Hilario Ruiz
Jose Andrada class Philippine Navy coastal patrol boat
The BRP Hilario Ruiz (PC-378) is the eighth ship of the Jose Andrada class coastal patrol boats of the Philippine Navy. It is part of the first batch of its class ordered through US Foreign Military Sales (FMS) in 1990, and was commissioned with the Philippine Navy on 1 June 1995. It was initially designated as Fast Patrol Craft, and was numbered "DF-378", but later on was re-designated as Patrol Gunboat "PG-378". Another round of reclassification was made in April 2016, which redesignated the patrol gunboat as the coastal patrol craft BRP Hilario Ruiz (PC-377).
Technical Details
The ship was built to US Coast Guard standards with aluminum hull and superstructure. She is powered by two Detroit Diesel 16V-92TA Diesel Engines with a combined power of around 2,800 hp driving two propellers for a maximum speed of 28 knots (52 km/h). Maximum range is 1,200 nmi (2,200 km) at 12 knots (22 km/h), or alternatively 600 nmi (1,100 km) at 24 knots (44 km/h).
The ship originally designed to carry one bow Mk.3 40 mm gun, one 81 mm mortar aft, and four 12.7 mm/50 caliber machine guns. Instead, she is armed with only four M2HB Browning 12.7 mm/50 caliber machine guns on Mk.26 mounts, with two positioned forward and two aft; and two M60 7.62 mm/30 caliber machine guns, both mounted amidships. The ship can carry 4,000 rounds of 12.7 mm and 2,000 rounds of 7.62 mm A large "Big Eyes" binocular is also carried on tripod mounts, one on the forecastle and one just above the mast.
Begin with the source’s own compact description: “BRP Hilario Ruiz” is jose Andrada class Philippine Navy coastal patrol boat. The dossier treats that line as a proposition to test through Hilario, Ruiz and Jose, not as a finished interpretation.
Why this record matters
The phrase “jose Andrada class Philippine Navy coastal patrol boat” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 14, 2026. The linked authority identifier is Q4836418. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1990, 1995 and 2016.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “BRP Hilario Ruiz”, its source revision and the description used here.
- Expand the search: follow BRP Hilario Ruiz primary sources, BRP Hilario Ruiz archive and Hilario research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “BRP Hilario Ruiz”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “BRP Hilario Ruiz” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.